* [gentoo-dev] How do you perform patchset versioning? @ 2011-05-25 13:34 Michael Haubenwallner 2011-05-25 13:40 ` [gentoo-dev] " Diego Elio Pettenò 0 siblings, 1 reply; 3+ messages in thread From: Michael Haubenwallner @ 2011-05-25 13:34 UTC (permalink / raw To: gentoo-dev Hello fellow developers, I'm wondering what is Best Practice to "tag" a bunch of patches stored in some VCS like [1], which are bundled into one single version of a patchset-tarball. My current usecase is: mico-2.3.13-r4[2] uses version 0.1 for the set of patches[3]. While I have to add a new patch into [3] (and bump to patchset-0.2), I still want to be able to recreate the patchset-0.1 content from VCS if necessary. My idea was to set a CVS-Tag on [3] for what is in each patchset version, but as I don't see /any/ (according to ViewVC) CVS-Tag on [1], I'm unsure... So what are your workflows here? Thank you! [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/ [2] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-misc/mico/mico-2.3.13-r4.ebuild?revision=1.1&view=markup [3] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/mico/2.3.13/ /haubi/ -- Michael Haubenwallner Gentoo on a different level ^ permalink raw reply [flat|nested] 3+ messages in thread
* [gentoo-dev] Re: How do you perform patchset versioning? 2011-05-25 13:34 [gentoo-dev] How do you perform patchset versioning? Michael Haubenwallner @ 2011-05-25 13:40 ` Diego Elio Pettenò 2011-05-25 15:26 ` Michael Haubenwallner 0 siblings, 1 reply; 3+ messages in thread From: Diego Elio Pettenò @ 2011-05-25 13:40 UTC (permalink / raw To: gentoo-dev Il giorno mer, 25/05/2011 alle 15.34 +0200, Michael Haubenwallner ha scritto: > > My idea was to set a CVS-Tag on [3] for what is in each patchset > version, but > as I don't see /any/ (according to ViewVC) CVS-Tag on [1], I'm > unsure... Tags are usually applied per-directory rather than on the whole repository, you can find tags for instance on http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/xine-lib/1.1.3_pre20060831/ For git-based projects (and I don't know if mico is), I have a preference to store a git tag with the patches applied over it, as I described on my blog: http://blog.flameeyes.eu/2010/09/07/maintaining-backports-with-git HTH! -- Diego Elio Pettenò — Flameeyes http://blog.flameeyes.eu/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] Re: How do you perform patchset versioning? 2011-05-25 13:40 ` [gentoo-dev] " Diego Elio Pettenò @ 2011-05-25 15:26 ` Michael Haubenwallner 0 siblings, 0 replies; 3+ messages in thread From: Michael Haubenwallner @ 2011-05-25 15:26 UTC (permalink / raw To: gentoo-dev On 05/25/2011 03:40 PM, Diego Elio Pettenò wrote: > Il giorno mer, 25/05/2011 alle 15.34 +0200, Michael Haubenwallner ha > scritto: >> >> My idea was to set a CVS-Tag on [3] for what is in each patchset >> version, but >> as I don't see /any/ (according to ViewVC) CVS-Tag on [1], I'm >> unsure... > > Tags are usually applied per-directory rather than on the whole > repository, you can find tags for instance on > > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/src/patchsets/xine-lib/1.1.3_pre20060831/ So I indeed just failed to find the tags - ok then. > For git-based projects (and I don't know if mico is), It is darcs based... > I have a > preference to store a git tag with the patches applied over it, as I > described on my blog: > > http://blog.flameeyes.eu/2010/09/07/maintaining-backports-with-git Thank you! -- Michael Haubenwallner Gentoo on a different level ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-05-25 15:27 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2011-05-25 13:34 [gentoo-dev] How do you perform patchset versioning? Michael Haubenwallner 2011-05-25 13:40 ` [gentoo-dev] " Diego Elio Pettenò 2011-05-25 15:26 ` Michael Haubenwallner
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox