On Tue, Feb 01, 2011 at 01:43:17AM +0100, Andreas Pakulat wrote: > I'm constantly doing the tag --contains and branch --contains thing to > find out when a certain fix was done at work to double-check wether a > reported bug is already contained in a released version. Or which > branches are affected by a bug introduced by a specific commit. > this could be implemented by a secondary merge tracking mechanism which works like svn's. git somewhat recently got the notes feature which allows attaching pretty much any textual metadata to commits without altering them. it's just that somebody would have to write that code ...
- Re: Merge or Cherry-Pick? Thiago Macieira
- Re: Merge or Cherry-Pick? Oswald Buddenhagen
- Re: Merge or Cherry-Pick? Thiago Macieira
- Re: Merge or Cherry-Pick? Oswald Buddenhagen
- Re: Merge or Cherry-Pick? Dawit A
- Re: Merge or Cherry-Pick? Thiago Macieira
- Re: Merge or Cherry-Pick? Aaron J. Seigo
- Re: Merge or Cherry-Pick? Thiago Macieira
- Re: Merge or Cherry-Pick? Aaron J. Seigo
- Re: Merge or Cherry-Pick? Andreas Pakulat
- Re: Merge or Cherry-Pick? Oswald Buddenhagen
- Re: Merge or Cherry-Pick? Thiago Macieira
- Re: Merge or Cherry-Pick? Alexander Neundorf
- Re: Merge or Cherry-Pick? Aaron J. Seigo
- Re: Merge or Cherry-Pick? Stefan Majewsky
- Re: Merge or Cherry-Pick? Aaron J. Seigo
- Re: Merge or Cherry-Pick? Andreas Pakulat
- Re: Merge or Cherry-Pick? Kevin Ottens
- Re: Merge or Cherry-Pick? Dawit A
- Re: Merge or Cherry-Pick? John Tapsell
- Re: Merge or Cherry-Pick? Dawit A
