On Tue, Jul 12, 2005 at 01:14:24AM -0700, Junio C Hamano wrote:
Marc Singer [EMAIL PROTECTED] writes:
# git-diff-cache HEAD
is really nice. But, do I really have to invoke git-update-cache with
every modified file? I could write a script to cul the filenames from
git-diff-cache
On Tue, Jul 12, 2005 at 11:33:36AM -0700, Dan Kohn wrote:
I apologize for what are probably obvious compilation questions, but I
suspect other newbies are encountering them as well. I'm having trouble
installing cogito 0.12.1 on both a vanilla Ubuntu box and on my account
on a FreeBSD
[EMAIL PROTECTED] /git git clone
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
linux-2.6
defaulting to local storage area
ssh: rsync: Name or service not known
fatal: unexpected EOF
I've read several messages that this is changing, but it still isn't
clear
On Mon, Jul 11, 2005 at 06:43:23PM -0700, Linus Torvalds wrote:
On Mon, 11 Jul 2005, Linus Torvalds wrote:
No, git-checkout-script _shouldn't_ have done that. It will do the
read-tree on the tag (which will do the right thing), but it won't change
the HEAD itself.
In preparation
On Mon, Jul 11, 2005 at 09:34:33PM -0700, Linus Torvalds wrote:
On Mon, 11 Jul 2005, Linus Torvalds wrote:
Of course, if you want to create a new branch my-branch and _not_
check it out, you could have done so with just
git-rev-parse v2.6.12^0
I switched to using the git version in source control.
Checkout/branching works great. :-)
But, this version of git doesn't let me do
# git checkout -f v2.6.11
error: Object 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c is a tree, not a commit
Needed a single revision
which I suspect is
In working through a usage example on my way to producing bonafide
patches, I've found that commit is complaining. Here's what I've done.
o Fetched and built cogito-0.12
o Fetched (rsync) Linus' tree
o Created a working directory, linux-2.6
o linked .git in the working directory to the
$ git checkout -f v2.6.11 ;# fixed one
warning: v2.6.11 is not a commit -- not updating your HEAD
$ git commit ;# to have his own baseline at v2.6.11
$ git-apply --index --stat --summary --apply ../old-patch-file
$ : do the usual tests
$ git commit ;# create a commit based on the
On Fri, Jul 08, 2005 at 06:08:52PM -0700, Junio C Hamano wrote:
MS == Marc Singer [EMAIL PROTECTED] writes:
MS Does this preclude symlinking .git? I'd like to keep one .git which
MS is mirrored from the net and allow for more than one working
MS directory.
I think people typically do
Jeff Garzik's guide doesn't appear to explain how to get patches back
out of the system.
I've successfully commited a set of changes.
# git diff HEAD^ HEAD
This command will produce a diff of the changes I've made. What is
the HEAD^? Does it refer to the commit before the last one made?
10 matches
Mail list logo
