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 mach
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 scri
# 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, but I'm having a hard time believing that that is how
others are preparing their commits.
-
To unsubscribe from this
On Mon, Jul 11, 2005 at 09:59:25PM -0700, Linus Torvalds wrote:
>
>
> On Mon, 11 Jul 2005, Marc Singer wrote:
> >
> > Does it make sense to think about this branch as an flow of commits?
> > Or is it just a starting point for a line of development?
>
> It&#x
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 protec
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 > .git/
On Mon, Jul 11, 2005 at 08:41:43PM -0700, Junio C Hamano wrote:
> When I start working on something I often do not know what the
> thing I am going to work on ends up to be. So I would start
> from v2.6.12 tag, do random hacking, and when I got into a
> reasonable shape, I would say ``Ok, this is
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
It complained when I cloned across devices.
`/git/cogito/.git/refs/tags/cogito-0.8' -> `.git/refs/tags/cogito-0.8'
cp: cannot create link `.git/refs/tags/cogito-0.8': Invalid cross-device link
`/git/cogito/.git/refs/tags/cogito-0.9' -> `.git/refs/tags/cogito-0.9'
cp: cannot create link `
On Mon, Jul 11, 2005 at 03:36:53PM -0700, Junio C Hamano wrote:
> Marc Singer <[EMAIL PROTECTED]> writes:
>
> > Looks like something's borked.
>
> Cogito I slurped about half hour ago has a quite different
> git-clone-script from your 4-line version. It is not s
On Fri, Jul 08, 2005 at 06:43:54PM -0700, Linus Torvalds wrote:
>
>
> On Fri, 8 Jul 2005, Marc Singer wrote:
> >
> > In working through a usage example on my way to producing bonafide
> > patches, I've found that commit is complaining. Here's what I&#x
On Mon, Jul 11, 2005 at 03:11:23PM -0700, Junio C Hamano wrote:
> Marc Singer <[EMAIL PROTECTED]> writes:
>
> > [EMAIL PROTECTED] /git > git clone
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > linux-2.6
> > defaulting
[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 wh
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?
If
On Fri, Jul 08, 2005 at 05:17:08PM -0700, Junio C Hamano wrote:
> >>>>> "MS" == Marc Singer <[EMAIL PROTECTED]> writes:
>
> MS> In working through a usage example on my way to producing bonafide
> MS> patches, I've found that commit is complai
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 f
> $ 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
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 .g
18 matches
Mail list logo
