* Petr Baudis ([EMAIL PROTECTED]) wrote:
> I'm happy to announce the release of the 0.12 version of the Cogito
> SCM-like layer over Linus' GIT tree history storage tool. Get it at
>
> http://www.kernel.org/pub/software/scm/cogito/
RPMs uploading to:
http://www.kernel.org/pub/soft
* John Ellson ([EMAIL PROTECTED]) wrote:
> "rpmbuild -ta cogito-0.12.tar.gz" fails because cogito.spec.in refers to
> ".bz2" in its "Source:" line, instead of to ".gz".
Just grab the .bz2, or the SRPM http://kernel.org/pub/software/scm/cogito/RPMS
(still mirroring, I just uploaded it a bit ago)
>
On 7/6/05, Jon Seymour <[EMAIL PROTECTED]> wrote:
> Ok, you asked for it:
>
> ...the GIT bucket.
>
> jon.
>
> ... ducks for cover ...
Groan ... as well you should.
My tree has re-appeared now. Thanks to whoever fixed it.
-Tony
-
To unsubscribe from this list: send the line "unsubscribe git"
Ok, you asked for it:
...the GIT bucket.
jon.
... ducks for cover ...
-
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
Linus Torvalds <[EMAIL PROTECTED]> writes:
> On Tue, 5 Jul 2005, Eric W. Biederman wrote:
>>
>> True but if you can you will get multiple tags with the
>> same suggested name. So you need so way to find the one you
>> care about.
>
> I do agree that it would make sense to have a "tagger" field w
http://www.kernel.org/git has stopped showing my linux-2.6 tree (the
"to Linus" one, my "test-2.6" tree is still there).
This is probably my fault ... but I'm not sure exactly why.
Here's what I did. Last Thursday I applied a set of patches ... and my "apply"
script choked on one of them. Some
Hi,
I've recently posted the following patches, in this order:
These ones are tidy ups:
[PATCH] Remove use of SHOWN flag
[PATCH] Move SEEN flag into epoch.h, replace use of VISITED flag with SEEN flag
[PATCH] Simplification - remove unnecessary list reversal from epoch.c
This series contains a
> This series contains a big fix, but assumes the tidy ups above have
> been applied:
That'd be a _bug_ fix
jon.
-
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
Applied the --merge-order, --max-age fix to fix
the --topo-order problem demonstrated by the test
case in the previous patch.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
rev-list.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
8238686fd422959dae50a908b3761aa545be1c4f
diff
Uncommented a test case that shows a --topo-order, --max-age break.
A subsequent patch witll fix this defect
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
t/t6003-rev-list-topo-order.sh | 20 ++--
1 files changed, 10 insertions(+), 10 deletions(-)
9b43fa5416abe653fd900a
Since --merge-order is the only thing that cares about the rev-list
parse order, change the rev-list list to match the parse order
and remove the corresponding compensating reversal from epoch.c.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
[PATCH] Move SEEN flag into epoch.h, replace use o
SEEN and VISITED do the same thing.
This change moves the SEEN flag into epoch.h, then replaces
uses of VISITED with SEEN and removes the definition
of the VISITED flag.
The merge-order code needs to clear the SEEN flag
set by the argument parsing to ensure correct
operation. So it clears that o
Now that duplicates are elided early, there is no need for the
SHOWN flag.
This patch removes the SHOWN flag and its uses from rev-list.c
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
rev-list.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
28294b1e139ea3f7c08814e022246e4
When we are cloning a repository on a local filesystem, it is
faster to just create a hard linkfarm of .git/object hierarchy
and copy the .git/refs files. By default, the script uses the
clone-pack method, but it can be told with the -l flag to do the
hard linkfarm (falling back on recursive file
This change ensures that git-rev-list --merge-order produces the same result
irrespective of what position the --merge-order argument appears in the argument
list.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
Linus: if you'd prefer to fix this a different way, that's fine by me!
---
rev-l
On Thu, 7 Jul 2005, Jon Seymour wrote:
>
> Linus: the last test fails with --topo-order at the moment. I haven't
> seen your most recent changes, so it may still fail for trivial
> reasons even then. If so, I'll post an update.
It passes for me, so I think the SEEN flag thing fixed it.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
Linus: the last test fails with --topo-order at the moment. I haven't
seen your most recent changes, so it may still fail for trivial
reasons even then. If so, I'll post an update.
t/t6003-rev-list-topo-order.sh | 417 +
When sed uses \n rather than ; as a separator (for BSD sed(1) compat),
it is cleaner to use a file directly, rather than an environment
variable containing \n characters.
This change changes t/t6000 write to sed.script directly and changes
the other tests to remove knowledge of sed.script.
Signe
> "LT" == Linus Torvalds <[EMAIL PROTECTED]> writes:
LT> But yeah, it's being a bit too anal. Just look at connect.c: shell_safe(),
LT> and add both '_' and '@' to the safe list (and any other safe characters),
LT> and off you go.
LT> And if somebody wants to add code to do proper escaping of
On Wed, 6 Jul 2005, Junio C Hamano wrote:
>
> Anybody who is interested in doing this can just move
> sq_expand() from diff.c to some public library and expose it in
> cache.h.
No, that doesn't work at all.
"sq_expand()" tries to protect things inside single quotes. That's a
totally different
On Wed, Jul 06, 2005 at 01:37:55PM -0700, Linus Torvalds wrote:
>
>
> On Wed, 6 Jul 2005, Greg KH wrote:
> >
> > I just updated to the latest git tree, and now get the following when I
> > try to pull from a ssh repo:
> >
> > $ git-pull-script [EMAIL PROTECTED]:/public_html/udev.git/
> > fatal
On Mon, 2005-07-04 at 14:32 +0200, Peter Osterlund wrote:
> I agree with the other comments, it's probably not wise to rely on
> wiggle, and wiggle sometimes makes a mess. However, it often does the
> right thing, and with a configurable merge program and an undo
> function, this should not be a pr
On Wed, 6 Jul 2005, Greg KH wrote:
>
> Ok, below is a patch for this. It works, but then errors out with:
> bash: git-upload-pack: command not found
> fatal: unexpected EOF
>
> So I'm guessing that I have to convince the server owner to update their
> version of git too?
The easie
On Wed, Jul 06, 2005 at 01:46:27PM -0700, Greg KH wrote:
> Ok, below is a patch for this. It works, but then errors out with:
> bash: git-upload-pack: command not found
> fatal: unexpected EOF
>
> So I'm guessing that I have to convince the server owner to update their
> version of gi
On Wed, 6 Jul 2005, Greg KH wrote:
>
> I just updated to the latest git tree, and now get the following when I
> try to pull from a ssh repo:
>
> $ git-pull-script [EMAIL PROTECTED]:/public_html/udev.git/
> fatal: I don't like '@'. Sue me.
>
> So I drop the @ and then get:
> $ git-pull-scrip
I just updated to the latest git tree, and now get the following when I
try to pull from a ssh repo:
$ git-pull-script [EMAIL PROTECTED]:/public_html/udev.git/
fatal: I don't like '@'. Sue me.
So I drop the @ and then get:
$ git-pull-script someserver.org:/public_html/udev.git/
fatal: I don't
"rpmbuild -ta cogito-0.12.tar.gz" fails because cogito.spec.in refers to
".bz2" in its "Source:" line, instead of to ".gz".
This is obviously a trivial patch. Do I need prior approval to send
patches to this group? What is the the significance of
"Signed-off-by:" Is there a FAQ I sho
Horst von Brand wrote:
John Ellson <[EMAIL PROTECTED]> wrote:
BUG: cg-clone accepts '_' in git+ssh: URI's, but cg-push does not.
Right. '_' is illegal in domain names...
OK, but its legal in the path part of URI's, I believe, and I'm more
bothered by the assymetry between cg-clone and cg
Hi, Junio C Hamano wrote:
> I wanted to have something like this in the past for some reason
> I do not exactly remember anymore, but basically it was to
> record "here is the list of related objects."
One use I'd have for that is regression testing -- collect all IDs in one
bag and then say "git
> "LT" == Linus Torvalds <[EMAIL PROTECTED]> writes:
LT> It would seem that you don't do anything at all for the non-local case.
Oops.
-
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Petr Baudis wrote:
> I don't know. Could you give some supporting argumentation, please? Is
> it really that hard to read for the Americans without the commas? It is
> at least harder to read for me as an European - we don't have any
> commas in there,
John Ellson <[EMAIL PROTECTED]> wrote:
> BUG: cg-clone accepts '_' in git+ssh: URI's, but cg-push does not.
Right. '_' is illegal in domain names...
--
Dr. Horst H. von Brand User #22616 counter.li.org
Departamento de Informatica Fono: +56 32 654431
Universid
This patch introduces an in-place topological sort procedure to commit.c.
Given a list of commits, sort_in_topological_order() will perform an in-place
topological sort of that list.
The invariant that applies to the resulting list is:
a reachable from b => ord(b) < ord(a)
This invarian
Swap the order of insert_by_date arguments so that it
matches the order of commit_list_insert.
This patch anticipates a future change which will call the
function via a pointer.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
commit.c |8
commit.h |6 +-
epoch.c
This patch adds a hacky special case to the rev-list main to restore the order
in which
the --merge-order sort algorithm receives arguments.
A subsequent patch will abstract this out more cleanly.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
rev-list.c |5 -
1 files changed, 4 i
Per a suggestion from Linus, I have introduced the rev_list_fns structure into
rev-list.c
The intent of this change is to make use of a strategy pattern to configure
the behaviour of git-rev-list and so help limit the ever-increasing
proliferation of boolean switches throughout the body of the
I have re-issued the patches I have created in the last day after checking
that they apply correctly when applied in this order to the
current Linus HEAD (b43d44779bf98977b211256f936d0edda8a9625a)
Introduction of --topo-order and tidy up of rev-list.c
[PATCH 1/13] Temporary fixup to rev-list.c t
This change is made so that gitk --all produces the same result for
every user irrespective of whether git-rev-parse --all produces
the same result for every user. By using --topo-order rather than
--merge-order this can be guaranteed and the existing (non-timestamp dependent)
behaviour of --merge
This patch introduces a --topo-order switch to git-rev-list.
When this --switch is specified, a minimal topological sort
weaker than the --merge-order sort is applied to the output
list.
The invariant of the resulting list is:
a is reachable from b => ord(b) < ord(a)
Signed-off-by: Jon
This patch introduces some unit tests for the git-rev-list --bisect
functionality.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
t/t6002-rev-list-bisect.sh | 247
1 files changed, 247 insertions(+), 0 deletions(-)
create mode 100755 t/t6002-r
git-rev-list --topo-order HEAD HEAD
caused a segmentation violation.
This has now been fixed.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
commit.c | 15 +++
commit.h |3 +++
epoch.h| 13 ++---
rev-list.c |8
4 files changed, 24 i
This patch implements a small tidy up of rev-list.c to reduce
(but not eliminate) the amount of ugliness associated
with the merge_order flag.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
Linus: I decided not to abstract this out as a function
as _too_ much abstraction can be a bad thing fr
This trivial patch removes the semicolon as the sed seperator in the
t/t6000-lib.sh test script
and replaces it with white space. This makes BSD sed(1) much happier.
Signed-off-by: Mark Allen <[EMAIL PROTECTED]>
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
I've applied this to the code th
This patch passes the test case introduced by the previous patch.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
epoch.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
6f7f90901ec4aafd12ac4179110b78fc426395cd
diff --git a/epoch.c b/epoch.c
--- a/epoch.c
+++ b/epoch.c
@@ -612,7
This test case demonstrates a problem with --merge-order.
A
|
B
|\
C D
|/
E
|
F
git-rev-list --merge-order A B doesn't produce the expected output of
A
B
D
C
E
F
The problem is fixed by a subsequent patch.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
t/t6001-rev-list-merge-order.sh |
Functions that are useful to other t6xxx testcases are moved into t6000-lib.sh
To use these functions in a test case, use a test-case pre-amble like:
. ./test-lib.sh
. ../t6000-lib.sh # t6xxx specific functions
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
t/t6000-lib.sh
On Wed, 6 Jul 2005, Junio C Hamano wrote:
>
> By invitation.
>
>
> When we are cloning a repository on a local filesystem [...]
Hmm.. Did you test the ssh case?
> +case "$local_use,$is_local" in
> +default,f)
> + ;;
It would seem that you don't do anything at all for the non
This test case demonstrates a problem with --merge-order.
A
|
B
|\
C D
|/
E
|
F
git-rev-list --merge-order A B doesn't produce the expected output of
A
B
D
C
E
F
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
This patch is known designed to apply on top of:
[PATCH 1/6] Temporary fixup to
This patch passes the test case in the first patch of this series.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
epoch.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
e4f793b932b30a7bee16610e311630515fe88330
diff --git a/epoch.c b/epoch.c
--- a/epoch.c
+++ b/epoch.c
@@ -612,
BUG: cg-clone accepts '_' in git+ssh: URI's, but cg-push does not.
I suggest '_' be added to the allowed character table in send-pack.c
John
-
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.o
Petr Baudis wrote:
Hello,
I'm happy to announce the release of the 0.12 version of the Cogito
SCM-like layer over Linus' GIT tree history storage tool. Get it at
http://www.kernel.org/pub/software/scm/cogito/
or cg-update if you have an older version cloned.
I wanted to release
This trivial patch removes the semicolon as the sed seperator in the
t/t6000-lib.sh test script
and replaces it with white space. This makes BSD sed(1) much happier.
Signed-off-by: Mark Allen <[EMAIL PROTECTED]>
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
I've applied this to the code th
This patch introduces some unit tests for the git-rev-list --bisect
functionality.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
t/t6002-rev-list-bisect.sh | 247
1 files changed, 247 insertions(+), 0 deletions(-)
create mode 100755 t/t6002-r
In message <[EMAIL PROTECTED]> Linus Torvalds wrote:
>
> If you make it print out its and then pause, you can use
>
> ls -l /proc//fd/
>
> to get an idea of what the files may be. Looks like the new perl version
> is leaking file descriptors..
It does. In case it's still of interest:
Functions that are useful to other t6xxx testcases are moved into t6000-lib.sh
To use these functions in a test case, use a test-case pre-amble like:
. ./test-lib.sh
. ../t6000-lib.sh # t6xxx specific functions
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
This patch series introduces test
IIRC our strategy was to let the users' umask take care of the
final mode bits. This patch fixes places that deviate from it.
Signed-off-by: Junio C Hamano <[EMAIL PROTECTED]>
---
apply.c|2 +-
csum-file.c|2 +-
entry.c|4 ++--
init-db.c |2 +-
receive-p
> "LT" == Linus Torvalds <[EMAIL PROTECTED]> writes:
LT> Anyway, as mentioned, you can certainly do a local clone a lot faster with
LT> "cp -rl" (and yes, I'll apply Junio's patch if he makes it available
LT> against the new version, and adds a flag to make it conditional),...
By invitation
The function write_one_ref() is passed the list of refs received
from the other end, which was obtained by directory traversal
under $GIT_DIR/refs; this can contain paths other than what
git-init-db prepares and would fail to clone when there is
such.
Signed-off-by: Junio C Hamano <[EMAIL PROTECTE
This patch implements a small tidy up of rev-list.c to reduce
(but not eliminate) the amount of ugliness associated
with the merge_order flag.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
Linus: I decided not to abstract this out as a function
as _too_ much abstraction can be a bad thing fr
Per a suggestion from Linus, I have introduced the rev_list_fns structure into
rev-list.c
The intent of this change is to make use of a strategy pattern to configure
the behaviour of git-rev-list and so help limit the ever-increasing
proliferation of boolean switches throughout the body of the
Swap the order of insert_by_date arguments so that it
matches the order of commit_list_insert.
This patch anticipates a future change which will call the
function via a pointer.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
commit.c |8
commit.h |6 +-
epoch.c
This patch adds a hacky special case to the rev-list main to restore the order
in which
the --merge-order sort algorithm receives arguments.
A subsequent patch will abstract this out more cleanly.
Signed-off-by: Jon Seymour <[EMAIL PROTECTED]>
---
rev-list.c |5 -
1 files changed, 4 i
Dear diary, on Wed, Jul 06, 2005 at 09:00:50AM CEST, I got a letter
where Frank Sorenson <[EMAIL PROTECTED]> told me that...
> Here is a patch to add a commify function to cg-Xlib. I'll follow
> this up with a patch that uses the new function to commify the
> number and size of objects pulled in
This patch introduces an in-place topological sort procedure to commit.c.
Given a list of commits, sort_in_topological_order() will perform an in-place
topological sort of that list.
The invariant that applies to the resulting list is:
a reachable from b => ord(b) < ord(a)
This invarian
This change is made so that gitk --all produces the same result for
every user irrespective of whether git-rev-parse --all produces
the same result for every user. By using --topo-order rather than
--merge-order this can be guaranteed and the existing (non-timestamp dependent)
behaviour of --merge
This patch introduces a --topo-order switch to git-rev-list.
When this --switch is specified, a minimal topological sort
weaker than the --merge-order sort is applied to the output
list.
The invariant of the resulting list is:
a is reachable from b => ord(b) < ord(a)
Signed-off-by: Jon
Hi,
Sven Verdoolaege:
> > to get an idea of what the files may be. Looks like the new perl version
> > is leaking file descriptors..
> >
> > Matthias?
>
> That was my mistake, actually.
> Thanks for spotting this.
>
Ouch. For me, the main danger of lots of Python programming is that
I tend not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a patch to commify the number and size of objects pulled
in cg-pull. Depends on the previous "Add commify function" patch.
Signed-off-by: Frank Sorenson <[EMAIL PROTECTED]>
Commify number and size of objects pulled in pull_progress
- ---
co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is a patch to add a commify function to cg-Xlib. I'll follow
this up with a patch that uses the new function to commify the
number and size of objects pulled in cg-pull.
Signed-off-by: Frank Sorenson <[EMAIL PROTECTED]>
Add a commify function
69 matches
Mail list logo
