lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1196262922.19921.20.camel@moss-terrapins.epoch.ncsc.mil>
Date:	Wed, 28 Nov 2007 10:15:22 -0500
From:	Dave Quigley <dpquigl@...ho.nsa.gov>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Tilman Schmidt <tilman@...p.cc>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: git guidance

There is a project listed on the kernel.org git page called guilt. I
find it very useful. It is much more responsive than stgit and it
actually has a git backend which quilt does not.

git-clone git://git.kernel.org/pub/scm/linux/kernel/git/jsipek/guilt.git

There is a tutorial associated with guilt which explains the commands
pretty well. The only thing that I find a problem with guilt is
sometimes I forget to pop/push the patches to the right place before
editing them. Actually that is less of a problem with guilt and more of
a problem with me :) Two of the main features that I find very useful
since I track the head of Linus's tree are guilt-rebase and then
guilt-patchbomb for sending patches.

On Wed, 2007-11-28 at 00:20 +0100, Jan Engelhardt wrote:
> On Nov 27 2007 23:33, Tilman Schmidt wrote:
> >
> >It didn't work too well. The first result was one of maximal
> >embarrassment: I produced a patch that didn't even compile when
> >applied to the official tree. This shouldn't happen with git, right?
> >Well, it did. So now I'm back to keeping a virgin kernel source tree
> >alongside my development area in order to produce diffs. That can't
> >be right?
> >
> No, it can't. Use stgit/quilt ;p
> 
> >Does somebody have a step by step tutorial for doing the standard
> >"edit - test - modify - retest - submit - edit - resubmit" sequence
> >with GIT? Is there a GIT newsgroup or mailinglist? Or should I just
> >post my silly questions to LKML?
> >
> http://www.linuxworld.com/video/?bcpid=1138309735&bclid=1213841149&bctid=1221911905
> 
> James Bottomley's intro helps a lot.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ