Sune Vuorela wrote:
On 2008-09-02, Andreas Schildbach [EMAIL PROTECTED] wrote:
Now, when I (or a co-maintainer) check out the project from SVN, I get
(as expected) a nearly empty project directory, containing just the
debian directory. But, how am I supposed to actually create the patches
On 2008-09-09, Michael Biebl [EMAIL PROTECTED] wrote:
while quilt push ; do quilt refresh ; done
quilt new 05_README_changes.diff
quilt edit README
quilt refresh
I assume you have set QUILT_PATCHES=3Ddebian/patches in ~/.quiltrc for
this to work properly?
yes. along with a lot of other
On Wed, 2008-09-03 at 15:06 +1000, Christopher Halse Rogers wrote:
The bzr equivalent of svn-buildpackage (the strangely named
bzr-builddeb) has a command bd-do which supports exactly this
use-case. For a merge-with-upstream package it exports the package,
then runs the command you specify in
On Wed, Sep 3, 2008 at 01:04, Andreas Schildbach [EMAIL PROTECTED] wrote:
Hello everyone,
I am maintaining a rather large package and have decided to use a
version control system (SVN).
I have already svn-inject'ed the existing package into my repository.
Since the original source is (in
On 2008-09-02, Andreas Schildbach [EMAIL PROTECTED] wrote:
Now, when I (or a co-maintainer) check out the project from SVN, I get
(as expected) a nearly empty project directory, containing just the
debian directory. But, how am I supposed to actually create the patches
that go into
On Wednesday 03 September 2008 05:04:12 Ben Finney wrote:
--cut--
I'm experimenting with Bazaar's loom feature, which allows a single
branch to contain multiple threads of development. A loom allows any
of the threads to be advanced, turned into separate patches as needed,
while still having a
also sprach George Danchev [EMAIL PROTECTED] [2008.09.03.1926 +0100]:
Yeah, rebase being very cool is sometimes abnormally used, so I'm
not sure you have choosen the right git counterpart to the bzr's
loom feature. It should be compared with topgit instead, which
self-maintained source package
Hello everyone,
I am maintaining a rather large package and have decided to use a
version control system (SVN).
I have already svn-inject'ed the existing package into my repository.
Since the original source is (in its current form) not re-distributable
(due to licensing issues), I decided to
Hi Andreas,
Le Wed, Sep 03, 2008 at 01:04:36AM +0200, Andreas Schildbach a écrit :
Now, when I (or a co-maintainer) check out the project from SVN, I get
(as expected) a nearly empty project directory, containing just the
debian directory. But, how am I supposed to actually create the
Andreas Schildbach [EMAIL PROTECTED] writes:
I am maintaining a rather large package and have decided to use a
version control system (SVN).
An unfortunate choice of VCS, since it is far behind more modern VCS
software for flexibility of management. Any of Git, Bazaar, Darcs, or
(perhaps)
Hi Ben,
Le Wed, Sep 03, 2008 at 01:04:12PM +1000, Ben Finney a écrit :
Andreas Schildbach [EMAIL PROTECTED] writes:
I am maintaining a rather large package and have decided to use a
version control system (SVN).
An unfortunate choice of VCS, since it is far behind more modern VCS
Charles Plessy [EMAIL PROTECTED] writes:
I would be especially interested by any replacement for this. I am
starting to wonder about the viability of keeping the whole upstream
sources in a VCS. If a non-redistributable file brought by a new
upstream release were accidentally commited (in my
On 9/3/08, Charles Plessy [EMAIL PROTECTED] wrote:
Hi Ben,
Le Wed, Sep 03, 2008 at 01:04:12PM +1000, Ben Finney a écrit :
Andreas Schildbach [EMAIL PROTECTED] writes:
I am maintaining a rather large package and have decided to use a
version control system (SVN).
An
13 matches
Mail list logo
