One problem against this is that configuration is sometimes user specific ( I occasionally switch to an alternate development branch for epic like streams, which I really should write as a gitflow command), I wouldnt really want that pushed upstream.
-- Sent from an Android On Dec 25, 2011 4:34 PM, "Aseem Kishore" <aseem.kish...@gmail.com> wrote:
> One problem against this is that configuration is sometimes user specific (
> I occasionally switch to an alternate development branch for epic like
> streams, which I really should write as a gitflow command), I wouldnt
> really want that pushed upstream.
> -- Sent from an Android
> On Dec 25, 2011 4:34 PM, "Aseem Kishore" <aseem.kish...@gmail.com> wrote:
> > Great idea! +1
> > Aseem
> > On Dec 24, 2011, at 10:06 PM, pro-lo...@optusnet.com.au wrote:
> > > Hi,
> > > I've recently started using git flow on windows, and I have to say, I
> > like it very much. Great work.
> > > One thing that I don't understand is why everybody who uses the same
> > repo has to run the git flow init command?
> > > Would it not be better to have a .gitflow file in the root of the
> > directory? Much like .gitignore, .gitattributes and .gitmodules?
> On Dec 24, 11:51 pm, Mark Derricutt <m...@talios.com> wrote: > > One problem against this is that configuration is sometimes user > specific ( > > I occasionally switch to an alternate development branch for epic like > > streams, which I really should write as a gitflow command), I wouldnt > > really want that pushed upstream.
> > -- Sent from an Android > > On Dec 25, 2011 4:34 PM, "Aseem Kishore" <aseem.kish...@gmail.com> > wrote:
> > > Great idea! +1
> > > Aseem
> > > On Dec 24, 2011, at 10:06 PM, pro-lo...@optusnet.com.au wrote:
> > > > Hi,
> > > > I've recently started using git flow on windows, and I have to say, I > > > like it very much. Great work.
> > > > One thing that I don't understand is why everybody who uses the same > > > repo has to run the git flow init command?
> > > > Would it not be better to have a .gitflow file in the root of the > > > directory? Much like .gitignore, .gitattributes and .gitmodules?
You don't have to run git flow init if the gitflow settings are cloned
over as well.
The reason you currently have to run git flow init, is the fact that
the configuration of gitflow is stored in the .git/conf file. This
file isn't cloned on git clone. Any other directory is, so when you
clone a gitflow enabled repo and do for example git flow feature start
my-feature, the feature branch prefix is know and is also consistent
with the original repo.
On Dec 25, 2:42 pm, Mark Derricutt <m...@talios.com> wrote:
