On Tue, Oct 29, 2013 at 10:09:53AM +1100, Benjamin Herrenschmidt wrote:
On Mon, 2013-10-28 at 09:59 +0100, Christoph Hellwig wrote:
Btw, can we please take away this discussion from ksummit-attendees? It's
got
absolutely nothing to do with kernel summit and is getting fairly annoying.
On Tue, Oct 29, 2013 at 10:09:53AM +1100, Benjamin Herrenschmidt wrote:
On Mon, 2013-10-28 at 09:59 +0100, Christoph Hellwig wrote:
Btw, can we please take away this discussion from ksummit-attendees? It's
got
absolutely nothing to do with kernel summit and is getting fairly annoying.
, when changes occur to the repostory format, please can
they be marked with some obvious subject so that folk know when things
are going to break?
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
break or change old formats, it only allows a new one.
Ah, ok. I thought it was a new requirement, and I had visions of
similar complaints about my repositories. Thanks for explaining
the situation.
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body
the difference against the _tree_, it shows
the difference against the index. Since cogito tries to hide the index
from you, cogito can't very well use that).
Ok, done.
Thanks Linus. I'll look forward to trying this out.
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git
On Wed, Jul 13, 2005 at 01:28:18PM -0700, Linus Torvalds wrote:
On Wed, 13 Jul 2005, Russell King wrote:
This says it all. 1min 22secs to generate a patch from a locally
modified but uncommitted file.
No, there's something else going on.
Most likely that something forced a total index
On Thu, Jul 14, 2005 at 10:08:31AM +0100, Catalin Marinas wrote:
Russell King [EMAIL PROTECTED] wrote:
it appears that cg-diff does a
git-update-cache --refresh /dev/null
each time it's run, which is taking the bulk of the time. Also note
that curiously, it exits with status 1
for it to ensure that
future breakages of this nature are caught. For me, cogito has been
extremely fragile, and I don't think the above usage is unreasonable.
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info
'
- `.git/objects/pack/pack-e3117bbaf6a59cb53c3f6f0d9b17b9433f0e4135.pack'
cg-pull: objects pull failed
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
;
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
workflow involves having an untouched local
copy of your tree and several trees for each area.
This involves updates using relative paths, and as has already been
found elsewhere, this (with cogito 0.12) doesn't work with packed
objects yet.
--
Russell King
-
To unsubscribe from this list: send
/objects/* directories. When new work is done in a tree, the
corresponding objects then appear, and only these objects need
transferring upstream.
It means that rsync --delete-after can (in theory) be used when
making changes available to the upstream maintainer.
--
Russell King
-
To unsubscribe
-2.6-arm.git to be fully populated
or are you happy for it to just grow the new objects as they become
available?
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
should ignore cogito's whinging about rsync being
deprecated?
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, Jul 09, 2005 at 10:58:18PM +0100, Russell King wrote:
On Thu, Jul 07, 2005 at 05:23:26PM -0700, Linus Torvalds wrote:
On Thu, 7 Jul 2005, Tony Luck wrote:
This is what happens (linus is a local branch just pulled from
kernel.org,
so it just contains one pack file and its index
.
And in the case of conflicts...?
If the baseline is a superset of the working tree, there will never be
any conflicts. Note that as I said above, this is a condition on doing
the pull in the first place.
How we determine that with git is another matter though. 8)
--
Russell King
-
To unsubscribe from
On Tue, Apr 19, 2005 at 10:23:41AM +0200, Petr Baudis wrote:
Dear diary, on Tue, Apr 19, 2005 at 09:02:51AM CEST, I got a letter
where Russell King [EMAIL PROTECTED] told me that...
My automatic pull this morning produced the following messages, which
seem to indicate that something's up
On Mon, Apr 18, 2005 at 10:23:32AM +0100, Russell King wrote:
On Sun, Apr 17, 2005 at 04:24:24PM -0700, Linus Torvalds wrote:
On Sun, 17 Apr 2005, Russell King wrote:
I pulled it tonight into a pristine tree (which of course worked.)
Goodie.
Note the pristine. Now comes the real
the following files:
0 files changed
through these ChangeSets:
From: Russell King: Mon Apr 18 22:50:01 BST 2005
[PATCH] ARM: Add missing new file for bitops patch
Signed-off-by: Russell King
--
Russell King
-
To unsubscribe from this list: send the line
On Tue, Apr 19, 2005 at 12:48:52AM +0200, Petr Baudis wrote:
Dear diary, on Mon, Apr 18, 2005 at 11:53:57PM CEST, I got a letter
where Russell King [EMAIL PROTECTED] told me that...
Maybe Petr can improve the error handling, and incorporate it (or at
least some of it) into git-pasky
7c4d75539c29ef7a9dde81acf84a072649f4f394
parent d5922e9c35d21f0b6b82d1fd8b1444cfce57ca34
author Russell King [EMAIL PROTECTED] 1113749462 +0100
committer Russell King [EMAIL PROTECTED] 1113749462 +0100
[PATCH] ARM: bitops
Convert ARM bitop assembly
On Sun, Apr 17, 2005 at 09:36:09AM -0700, Linus Torvalds wrote:
On Sun, 17 Apr 2005, Russell King wrote:
On Sat, Apr 16, 2005 at 04:01:45PM -0700, Linus Torvalds wrote:
So I re-created the dang thing (hey, it takes just a few minutes), and
pushed it out, and there's now an archive
on their accessibility? I wonder if this has an effect
here.
(or what about any other security model?)
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
on the umask.
If this is so, please note that git appears to track the file modes,
and any dependence upon the umask is likely to screw with this tracking.
--
Russell King
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info
24 matches
Mail list logo
