, based on master
Remaining questins:
- Is the above workflow good?
- Wasn't there also a debian branch for some purpose?
- I've read, that it would be possible somehow to reexport old patches with
topgit? How?
- How can I work on an older release of solr with this setup?
Best regards,
Thomas
, as dpkg-
source uses them in version 3
- Integrates with git-buildpackage
- Doesn't need anything, that topgit hasn't ATM
Todo
discuss, test, script
Best regards,
Thomas Koch, http://www.koch.ro
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss
happily accept anybody else steping in to present the topic.
Best regards,
Thomas Koch, http://www.koch.ro
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss
to be done. :-)
Best regards,
Thomas Koch, http://www.koch.ro
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss
Petr Baudis:
On Mon, Mar 22, 2010 at 08:59:40AM +0100, Thomas Koch wrote:
In all three cases you're free to either keep or throw away the old
patchset.
Yes, but to the same degree e.g. with StGIT I'm free to keep the head of
the old patch series. That does not mean the operation
CC: debian-devel. Please subscribe to vcs-pkg-discuss@lists.alioth.debian.org
to follow this topic!
martin f krafft:
also sprach Thomas Koch tho...@koch.ro [2011.07.30.1229 +0200]:
Martin F. Krafft (madduck) was so kind to remind me posting this here.
We're right now at debconf discussing
Thomas Koch:
I had some time on my way back to think about patch bases. Is it right,
that it isn't actually necessary to save the commit sha-1s of patch bases?
It is my understanding that you could calculate them:
1. $CANDIDATE=$(git merge-base --octopus $DEPENDENCY_NAMES)
2. for each
