it seems like a
good fit. (rssh, tf5, and xfonts-jmk.)
--
Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle/
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo
will send me, whereas this year I won't make it since I'd
probably have to fund my own way on top of the really long economy-class
flight.)
--
Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle/
___
vcs-pkg-discuss mailing list
vcs-pkg
packaging, I'm undecided on these two options:
1. Build-depend on automake and let it rebuilt itself at 'make' time
Definitely the right solution IMO. This is what I do with all of my
packages.
--
Russ Allbery (r...@stanford.edu) http://www.eyrie.org/~eagle
upstream; I would find that an
unacceptable burden.
True. I've not yet had topic branches with conflicts between them.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/
___
vcs-pkg-discuss mailing list
vcs-pkg-discuss
martin f krafft [EMAIL PROTECTED] writes:
also sprach Russ Allbery [EMAIL PROTECTED] [2008.11.18.0056 +0100]:
Rather than using rerere, I create a temporary merge branch based off
upstream and merge each topic branch into it in sequence, and then
merge the temporary merge branch
into the integration branch, which seems to
accomplish the same thing (not having to re-handle the merge conflicts
when merging the first topic branch).
Otherwise, I use the same approach.
--
Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle
so that we can reference each
layout with a clear name. If this is so, I believe this is the right
place where to attempt defining such a set.
FWIW, I've been keeping notes on what I'm personally doing at:
http://www.eyrie.org/~eagle/notes/debian/git.html
--
Russ Allbery ([EMAIL PROTECTED
