On 22/7/10 20:23, "Alan Hawrylyshen" <a...@polyphase.ca> wrote:

> On Jul 19, 2010, at 09:29, Roddie Grant wrote:
> 
>> My recent brush with a forgotten stash has led me to consider again an issue
>> which I've never really got a complete answer to - how much information (if
>> any) about a project should be kept outside Git.
>> 
>> IOW do developers keep a note (on paper, spreadsheet, database?) of how
>> branches inter-relate, their purpose and so on.
> 
> yes - absolutely - for any sizable project, I typically have an issue tracker
> (redmine, jira, bugzilla, trac, whatever) and an open issue for every defect
> and planned unit of work (feature, etc).
<snip>
> We don't delete these branches, since they capture the development history.
> 
Thanks Alan. I'll have to look at closer integration between issue tracker
and Git. Do you get duplication of information between Git and your issue
tracker?

If you have a branch for every issue and every feature and then never delete
them, don't you end up with an unmanageable number of branches?

Roddie


-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-us...@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to