On Fri, May 16, 2008 at 04:04:20PM -0400, Joey Hess wrote:
Raphael Hertzog wrote:
I totally agree that we need to make our changes more visible. In the
openssl case, the patch in question is inside the .diff.gz and you don't
notice it in the unpacked source package. I tend to give a look to
On Wed, Jul 16, 2008 at 12:04:38AM +0200, Stefano Zacchiroli wrote:
On Tue, Jul 15, 2008 at 01:45:16PM -0700, Russ Allbery wrote:
[..snip..]
FWIW, I've been keeping notes on what I'm personally doing at:
http://www.eyrie.org/~eagle/notes/debian/git.html
Very interesting reading!
This
On Mon, Sep 29, 2008 at 08:43:18AM +0200, martin f krafft wrote:
[..snip..]
If git-buildpackage expects master, then it is inflexible; you
should be able to tell it to build from build.
git-buildpackage builds from any branch you tell it to.
-- Guido
On Tue, Sep 30, 2008 at 10:27:13PM +0200, Martin Bähr wrote:
On Tue, Sep 30, 2008 at 02:27:34PM -0500, Manoj Srivastava wrote:
Not really. I prefer to have the source packages be unpackged
even on a machine which does not run Debian, using just plain old tar
and patch. Thus I tend
Hi,
I think i'd be nice if once could link changelog entries back to VCS
commits more easily (to see how a bug actually got fixed). Git-dch has
support for including parts of the SHA1 for some time so together with
Vcs-Browser we can easily link back to the VCS:
On Wed, Nov 12, 2008 at 01:20:10PM +0100, Stefano Zacchiroli wrote:
Following the (good) path of Closes, it should probably be something
like [Commit: fed3f3d]. Also, can't it be put inside the same
parentheses than Closes, as in (Closes: #7005180, #7005181; Commit:
fed3f3d).
If we really want
On Wed, Nov 12, 2008 at 11:09:45AM -0500, James Westby wrote:
On Wed, 2008-11-12 at 08:39 +0100, martin f krafft wrote:
also sprach Guido Günther [EMAIL PROTECTED] [2008.11.08.1419 +0100]:
Does this look like a worthwhile extension to the current changelog
format? For me it makes
On Fri, Nov 14, 2008 at 07:42:02AM +0100, martin f krafft wrote:
also sprach Martin Bähr [EMAIL PROTECTED] [2008.11.13.1540 +0100]:
On Thu, Nov 13, 2008 at 01:42:44PM +0100, martin f krafft wrote:
Except, of course, there is no such thing as an SVN-Commit. r123
is a state, a snapshot, the
On Sun, May 24, 2009 at 03:57:04PM +0200, Stefano Zacchiroli wrote:
On Sat, May 23, 2009 at 12:55:57AM +0200, martin f krafft wrote:
Now:
- all patches are saved in debian/patches/ and can be used directly with
quilt.
Yes, and you can use TopGit to actually develop features on all
Hi Martin,
On Mon, May 25, 2009 at 10:52:42AM +0200, martin f krafft wrote:
1. due to the rebasing, it's not possible to work with other people,
unless everyone maintains their own patch queue.
Not true. You just have to agree beforehand what branches do keep the
patch queues (therefore the
On Tue, Aug 04, 2009 at 04:37:46PM +, Frédéric Brière wrote:
martin f krafft madd...@debconf.org wrote:
The workflows I know currently are: my topgit workflow, Mehdi's
quilt workflow, and Guido's git-buildpackage approach. There my
be others.
Aren't Mehdi and Guido basically
Hi Stéphane,
On Wed, Aug 05, 2009 at 07:31:13PM +0200, Stéphane Glondu wrote:
Guido Günther a écrit :
Looks pretty similar to what I do except that you use upstream while I
use the debian branch as the base.
This is done on purpose ;-)
thought so ;) this wasn't ment as criticism, i'm just
Hi Ian,
On Wed, Sep 28, 2016 at 11:09:03AM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Re: Intent to commit craziness - source package
> unpacking"):
> > Thanks for your comments. I feel unblocked :-).
>
> So, I now intend to go and implement my plan.
>
> There will be a little while
Hi Ian,
On Mon, Oct 03, 2016 at 04:15:08PM +0100, Ian Jackson wrote:
[..snip..]
> Because I'm a pernickety type of person I reviewed the dependencies of
> git-buildpackage. I have some qualms about the following
> dependencies:
>
> Recommends: pristine-tar (>= 0.5)
>
> pristine-tar has
14 matches
Mail list logo
