| From | Subject | Date |
|---|---|---|
| Eric Wong | [PATCH 1/2] git-svn: add --prefix= option to multi-init
Also, document --{trunk,branches,tags} options while we're
documenting multi-init options.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
---
Documentation/git-svn.txt | 18 ++++++++++++++++++
git-svn.perl | 8 +++++---
2 files changed, 23 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index ce63def..8df43cb 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -139,6 +139,24 @@ manually joining b...
| Jan 7, 11:35 pm 2007 |
| Eric Wong | [PATCH 2/2] git-svn: pass an unambiguous ref to rev-list whe...
Some users apparently create local heads with the same basename
as the remote branch they're tracking.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
---
git-svn.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index a092be8..56f1700 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -1086,7 +1086,7 @@ sub graft_merge_msg {
my ($grafts, $l_map, $u, $p, @re) = @_;
my $x = $l_map->{$u}->{$p};
- my $rl = rev_list_raw($...
| Jan 7, 11:35 pm 2007 |
| Junio C Hamano | [ANNOUNCE] GIT 1.4.4.4
The latest maintenance release GIT 1.4.4.4 is available at the
usual places:
http://www.kernel.org/pub/software/scm/git/
git-1.4.4.4.tar.{gz,bz2} (tarball)
git-htmldocs-1.4.4.4.tar.{gz,bz2} (preformatted docs)
git-manpages-1.4.4.4.tar.{gz,bz2} (preformatted docs)
RPMS/$arch/git-*-1.4.4.4-1.$arch.rpm (RPM)
This is to push out a handful bugfixes since 1.4.4.3.
On the 'master' development front, the stabilization for v1.5.0
will start soonish.
---------------------------------...
| Jan 7, 11:30 pm 2007 |
| Jakub Narebski | Bug (?) in setting values with git-repo-config
Currently there is no way to set up configuration variable to a value with
preceding whitespace, trailing whitespace, or one of comment delimiters
('#' or ';'). And one can't use "..." for that, because even encompassing
doublequotes gets escaped.
I think that git-repo-config should detect if value needs to be quoted, and
do that automatically...
$ declare -x GIT_CONFIG=gitconf
$ git repo-config section.key "value with # inside"
$ git repo-config --get section.key
value wit...
| Jan 7, 10:41 pm 2007 |
| David Woodhouse | Re: OT: character encodings
See the 'i18n.commitencoding' property, stored in the repository config
and defaulting to UTF-8. Git is certainly capable of converting to its
internal storage encoding when you commit; if it doesn't do so by
default then that would be a bug.
--
dwmw2
-
| Jan 7, 9:53 pm 2007 |
| Jakub Narebski | Re: How git affects kernel.org performance
It can point to both. Usually it is either unset, and then we
do find over $projectroot, or it is a file (URI escaped path
relative to $projectroot, SPACE, and URI escaped owner of a project;
you can get the file clicking on TXT on projects_list page).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
-
| Jan 7, 9:51 pm 2007 |
| Jakub Narebski | Re: [DRAFT] Branching and merging with git
Added to
http://git.or.cz/gitwiki/GitDocumentation
http://git.or.cz/gitwiki/GitLinks
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
-
| Jan 7, 9:22 pm 2007 |
| Martin Langhoff | [PATCH] cvsimport: skip commits that are too recent
With this patch, cvsimport will skip commits made
in the last 10 minutes. The recent-ness test is of
5 minutes + cvsps fuzz window (5 minutes default).
When working with a CVS repository that is in use,
importing commits that are too recent can lead to
partially incorrect trees. This is mainly due to
- Commits that are within the cvsps fuzz window may later
be found to have affected more files.
- When performing incremental imports, clock drift between
the systems may lead to skipped ...
| Jan 7, 9:11 pm 2007 |
| Junio C Hamano | Re: [PATCH] cvsimport: skip commits that are too recent
Hmmmmm. This is good for tracking other people's work, but, I
am not quite sure how well it works with my workflow.
I have a CVS upstream, but I manage my own development with git.
I start my day by running an incremental cvsimport, rebase my
branch on top of whatever at the tip of the cvsimport branch. I
use cvsexportcommit (actually a moral equivalent of it I've been
using before cvsexportcommit has become part of git) to make
parts of my branch that are ready for other people's consumption
...
| Jan 7, 9:59 pm 2007 |
| Martin Langhoff | Re: [PATCH] cvsimport: skip commits that are too recent
That probably means I should have added a
--force-fetch-all-and-i-mean-it flag to override the cautious
behaviour. I'll repost ina few hours, with doco too.
I'll try harder next time ;-)
cheers
martin
-
| Jan 7, 10:13 pm 2007 |
| Junio C Hamano | Re: [PATCH] cvsimport: skip commits that are too recent
Well I meant to say that my conclusion is that that flag is not
-
| Jan 7, 10:19 pm 2007 |
| Martin Langhoff | Re: [PATCH] cvsimport: skip commits that are too recent
you are getting soft in your old age, man :-)
More seriously, as soon as I sent the patch I thought of the use case
you describe. Not everyone is as patient as you are, and someone may
have things scripted. If the cvs repo is local/fast and under your
control, it doesn't make sense to be _so_ conservative.
Also -- by having the flag we get an excuse to mention it in the doco.
m
-
| Jan 7, 11:18 pm 2007 |
| Jakub Narebski | [PATCH] gitweb: Remove superfluous "|" in "commit" view
Remove superfluous trailing "|" separator from difftree part of "commit"
view for new files (created in given commit).
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
gitweb/gitweb.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index f46a422..25e5079 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -2239,7 +2239,7 @@ sub git_difftree_body {
}
print $cgi->a({-href => href(action=>"bl...
| Jan 7, 9:10 pm 2007 |
| Johannes Schindelin | [PATCH 2/2] Teach the revision walker to walk by reflogs wit...
When called with "--walk-reflogs", as long as there are reflogs
available, the walker will take this information into account, rather
than the parent information in the commit object.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
I do not have any idea if this will help bisecting through
reflogs...
Also, this is only lightly tested on the hard cases: circular
reflogs, ranges, and mixed logging (log overlapping reflogged and
non-reflogged revisions).
Ma...
| Jan 7, 9:02 pm 2007 |
| Johannes Schindelin | [PATCH 1/2] Sanitize for_each_reflog_ent()
It used to ignore the return value of the helper function; now, it
expects it to return 0, and stops iteration upon non-zero return
values; this value is then passed on as the return value of
for_each_reflog_ent().
Further, it makes no sense to force the parsing upon the helper
functions; for_each_reflog_ent() now calls the helper function with
old and new sha1, the email, the timestamp & timezone, and the message.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---
...
| Jan 7, 8:59 pm 2007 |
| Junio C Hamano | Re: [PATCH 1/2] Sanitize for_each_reflog_ent()
Perhaps. I did it that way deliberately because all existing
users did not have to pay overhead of parsing.
Thanks. Will queue in 'pu' initially as I do not have much time
to look at it tonight.
-
| Jan 7, 9:46 pm 2007 |
| J. Bruce Fields | [PATCH] Documentation: clarify glossary definition of "reach...
Clarify glossary definition of "reachable" (what chain?)
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
---
Documentation/glossary.txt | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/glossary.txt b/Documentation/glossary.txt
index 7c1a659..5886fa7 100644
--- a/Documentation/glossary.txt
+++ b/Documentation/glossary.txt
@@ -236,7 +236,7 @@ push::
reachable::
An object is reachable from a ref/commit/tree/tag, if there is a
- chain ...
| Jan 7, 8:28 pm 2007 |
| Junio C Hamano | Re: [PATCH] Documentation: clarify glossary definition of "r...
That is better but the description is too commit centric.
The set of reachable objects from a tag is the tag
itself and the set of reachable objects from the object
it tags. The set of reachable objects from a commit is
the commit itself, and the set of reachable objects from
its parents and its tree. The set of reachable objects
from a tree is the tree itself, and the set of reachable
objects from the trees and blobs contained within it.
...
| Jan 7, 9:44 pm 2007 |
| J. Bruce Fields | Re: [PATCH] Documentation: clarify glossary definition of "r...
Oops, you're right! Take two: (I'm still giving the commit case first
as a special example, because I think it's the most important case, and
because it requires less knowledge to understand.)
--b.
From 1b1885dc3cf597452c597f34e6f52856c9524239 Mon Sep 17 00:00:00 2001
From: J. Bruce Fields <bfields@citi.umich.edu>
Date: Sun, 7 Jan 2007 19:25:35 -0500
Subject: [PATCH] [PATCH] Documentation: clarify definition of "reachable"
Clarify definition of "reachable" (what chain?)
Signed-off...
| Jan 7, 11:28 pm 2007 |
| Sean | Re: OT: character encodings (was: Linux 2.6.20-rc4)
On Sun, 7 Jan 2007 15:05:53 -0500
Dave Jones <davej@redhat.com> wrote:
-
| Jan 7, 4:15 pm 2007 |
| Jan Engelhardt | Re: OT: character encodings (was: Linux 2.6.20-rc4)
No, LC_CTYPE defines what charset you use. (I may be wrong, though.)
-`J'
--
-
| Jan 7, 4:40 pm 2007 |
| Xavier Bestel | Re: OT: character encodings (was: Linux 2.6.20-rc4)
Le dimanche 07 janvier 2007
| Jan 7, 5:07 pm 2007 |
| Linus Torvalds | Re: How git affects kernel.org performance
Won't help. ext3 does NO readahead at all. It doesn't use the general VFS
helper routines to read data (because it doesn't use the page cache), it
just does the raw buffer-head IO directly.
(In the non-indexed case, it does do some read-ahead, and it uses the
generic routines for it, but because it does everything by physical
address, even the generic routines will decide that it's just doing random
reading if the directory isn't physically contiguous - and stop reading
ahead).
(I ma...
| Jan 7, 3:35 pm 2007 |
| Baz | [BUG] cogito: cg-push fails when using stg
Hi,
I've been using cogito and stg together on cairo and I ran into
problems attempting to do a cg-push.
$ cg-push
error: src refspec master matches more than one.
fatal: unexpected EOF
It turns out this is matching refs/heads/master and refs/bases/master;
the second of these is an stg artifact, but not the current branch. I
think there's a bug in cogito here, in cg-Xlib:
[ ! -s "$_git/HEAD" ] || { _git_head="$(git-symbolic-ref HEAD)";
_git_head="${_git_head#refs/heads/}"; }
This sets _gi...
| Jan 7, 2:57 pm 2007 |
| Nicolas Pitre | [PATCH] "init-db" can really be just "init"
Make "init" the equivalent of "init-db". This should make first GIT
impression a little more friendly.
Signed-off-by: Nicolas Pitre <nico@cam.org>
---
I'm resending this as I think this is still pertinent and I cannot
remember what the initial issue against this was and whether it is still
valid.
This would be a nice rule of thumb to try to have all porcelainish
commands not have any hyphen in their name, like "diff", "commit",
"add", "rm", "checkout", etc. ?
diff --git a/Docu...
| Jan 7, 1:31 pm 2007 |
| Alan Chandler | problem with Documentation/hooks.txt
I was just looking at the documentation of the post-commit hook in order
to fix a problem on one of my repositories and I came across this:-
"The default 'post-commit' hook, when enabled, demonstrates how to
send out a commit notification e-mail."
So I went looking in the templates/hooks--post-commit file and it has
nothing (literally :-) ).
and as far as I can see looking over git's history it has always been
like that.
I don't have an example to submit a patch - but I am sure lots of pe...
| Jan 7, 7:13 am 2007 |
| Martin Waitz | Re: problem with Documentation/hooks.txt
hoi :)
Have a look at the 'update' hook instead.
Where have you found this hint? We should change the documentation here.
--=20
Martin Waitz
| Jan 7, 8:34 am 2007 |
| Nicolas Vilz | Re: problem with Documentation/hooks.txt
May I repeat my ignored request to check the update-hook-example in
Documentation/howto/ for working correctly? It doesn't.
I am no bash guru, but as far as i understand the code, the size of an
argument is checked with matchlen. That is imho bad for regexp.
I built the scenario described there and i couldn't commit to the tmp/*
branches. I also couldn't commit to the bw/ topics and i couldn't tag
anything as the specific role proposed in this example.
as long as the length of the refs-stri...
| Jan 7, 11:28 am 2007 |
| Alan Chandler | Re: problem with Documentation/hooks.txt
Documentation/hooks.txt (under the post-commit hook section)
--
Alan Chandler
http://www.chandlerfamily.org.uk
-
| Jan 7, 10:41 am 2007 |
| Chris Lee | Simple UI question...
Hey guys,
So I'm trying to figure out the best way to pull out a checkout of the
entire tree as of a given revision ID. I have a whole bunch of
revision IDs, and I'd like to know what the git equivalent of (say)
the following is:
svn co -r280600 file:///path/to/svn/repo
For the sake of argument, let's say that r280600 imported as
07058310db903317faa300b93004a5a2e0fc2dcc into my git tree.
How do I get a pristine checkout in my working copy of the entire tree
as the repository saw it at 07058...
| Jan 7, 7:02 am 2007 |
| Josef Jeff Sipek | Re: Simple UI question...
I have great success with:
git-reset --hard $hash
Jeff.
--
#endif /* NO LIFE */
-
| Jan 7, 7:06 am 2007 |
| Junio C Hamano | Re: Simple UI question...
These two do vastly different things (but the latter is flawed
and does _not_ do what it is trying to do).
- If this checkout is just to look-see, and if you are on a
branch that is precious to you (say, you intend to keep
importing from svn or other repository onto that branch),
then you should use a temporary branch. Eric's suggestion is
this approach -- but "git checkout -b $branch $start" is
about CREATING a new branch, so once you used the temporary
branch name, you cann...
| Jan 7, 7:30 am 2007 |
| Shawn O. Pearce | Re: Simple UI question...
One way is:
git archive \
--format=tar \
07058310db903317faa300b93004a5a2e0fc2dcc \
| (mkdir ../export; cd ../export; tar xf -)
Would give you a new directory tree which is not related to any
Git repository, but which contains the exact set of files in 070583.
Yes, that is usually the way you do this. Unlike the archive trick
above the result will be in your current working directory and
will be associated with the current Git repository. Further you
That's just cruel. I...
| Jan 7, 7:13 am 2007 |
| Chris Lee | Re: Simple UI question...
Heh. He's going to kill me for continuing to drag his name throught he
What I've been doing is 'rm -rf *' from the working directory and
Eric's shows the same problem - for some revision IDs, when I do a
I assume 'removing everything in the working tree' counts as "local
modifications"? :)
-
| Jan 7, 7:21 am 2007 |
| Shawn O. Pearce | Re: Simple UI question...
Yes! That's what's going wrong. Don't do "rm -rf *". Let Git take
care of the empty directories for you. If Git deletes all source
files in that directory (as they don't belong in this version that
you are checking out) it will also delete the now empty directory.
The only time it fails is if you are on Windows and some process
has the directory busy. :-)
--
Shawn.
-
| Jan 7, 7:29 am 2007 |
| Chris Lee | Re: Simple UI question...
So, if I were starting with an empty working directory, and I had just
synced over the .git folder from the place where I'm doing the actual
importing - how would I populate the working directory with a copy of
the contents of the tree from (say)
07058310db903317faa300b93004a5a2e0fc2dcc ?
-
| Jan 7, 7:38 am 2007 |
| Junio C Hamano | Re: Simple UI question...
git reset --hard 070583
-
| Jan 7, 7:40 am 2007 |
| Chris Lee | Re: Simple UI question...
Okay, thanks :)
(I don't really care about trying to do actual development on any of
the branches that I've imported - I mostly am interested in finding
out some numbers on things like 'How much faster is git when rewinding
the directory tree to a given commit ID?' and related issues.)
-
| Jan 7, 7:50 am 2007 |
| Stefan-W. Hahn | Re: problem with git clone on cygwin
--
Stefan-W. Hahn It is easy to make things.
/ mailto:stefan.hahn@s-hahn.de / It is hard to make things simple.
-
| Jan 7, 5:30 am 2007 |
| Juergen Ruehle | Re: problem with git clone on cygwin
Stefan-W. Hahn writes:
> Also sprach Juergen Ruehle am Sat, 06 Jan 2007 at 22:40:52 +0100:
> > Could you enumerate the other compatability problems?
>
> The problem that one cannot use one version of cygwin.dll and
> simultaniously another (incomatible) version. (Having a local
> installed cygwin window open and trying to build in a branch where
> another version is used.)
Yes that is an unfortunate (though probably unavoidable) downside of
cygwin. But my question ...
| Jan 7, 6:46 am 2007 |
| Stefan-W. Hahn | Re: problem with git clone on cygwin
Non, its just the above metioned incompatibility between the cygwin
I sent out a patch using mmap() instead of pread() if configured.
--
Stefan-W. Hahn It is easy to make things.
/ mailto:stefan.hahn@s-hahn.de / It is hard to make things simple.
-
| Jan 7, 7:21 am 2007 |
| Songmao Tian | troubles in supersede old development history (git-svn)
our trunk's maintainer is lazy in merging branches, I'd like to merge
the branch kkmao, and now there are so many the conflicts. I want to
just use my version and overcome all the conflicts.
i try in this way:
git-checkout -b trunk remotes/trunk
git-rebase --merge -s ours remotes/kkmao
git-svn dcommit -i trunk
diff-tree 9b75e30191838431810aec4eda98482a8d6935ed~1
9b75e30191838431810aec4eda98482a8d6935ed
Transaction is out of date: Out of date:
'trunk/Targets/Bonito/conf/Bonito.lmbox' in transac...
| Jan 7, 5:29 am 2007 |
| Eric Wong | Re: troubles in supersede old development history (git-svn)
Probably obvious, but is remotes/trunk up-to-date with git-svn fetch?
Next, can you ensure that the tree referenced by
9b75e30191838431810aec4eda98482a8d6935ed~1 (note the ~1) is the same
as remotes/trunk?
(git diff 9b75e30191838431810aec4eda98482a8d6935ed~1 remotes/trunk)
Unfortunately, I'm not familiar with how the 'ours' strategy works with
rebase --merge. I generally use the default recursive. Can you look
at the history in gitk to see if the history from refs/remotes/trunk
Just look a...
| Jan 7, 10:44 pm 2007 |
| Junio C Hamano | Moving initialization of log_all_ref_updates
The patches to prevent Porcelainish that require working tree
from doing any damage in a bare repository make a lot of sense,
and I want to make the is_bare_git_dir() function more reliable.
In order to allow the repository owner override the heuristic
implemented in is_bare_git_dir() if/when it misidentifies a
particular repository, it would make sense to introduce a new
configuration variable "[core] bare = true/false", and make
is_bare_git_dir() notice it.
The scripts would do a 'repo-config ...
| Jan 7, 5:24 am 2007 |
| Shawn O. Pearce | Re: Moving initialization of log_all_ref_updates
Which will come up right most of the time. And when it doesn't,
core.bare is there to bail the user out. I like it.
Do we want to consider having init-db/clone set core.bare based on
Ack'd. There's little we can do here then to change the order things
get invoked. That's harder and uglier to change than to just declare
"we don't know what this right now" and guess later. I'd go with
the patch you have now. Maybe post 1.5.0 we can cleanup some of the
init order to get the config file par...
| Jan 7, 5:37 am 2007 |
| Junio C Hamano | Re: Moving initialization of log_all_ref_updates
Here is what I have as a follow-up patch to the one you are
responding to.
--
diff --git a/builtin-init-db.c b/builtin-init-db.c
index 97fd82f..e78222f 100644
--- a/builtin-init-db.c
+++ b/builtin-init-db.c
@@ -252,9 +252,13 @@ static int create_default_files(const char *git_dir, const char *template_path)
}
git_config_set("core.filemode", filemode ? "true" : "false");
- /* Enable logAllRefUpdates if a working tree is attached */
- if (!is_bare_git_dir(git_dir))
+ if (is_bare_reposi...
| Jan 7, 5:54 am 2007 |
| Shawn O. Pearce | Re: Moving initialization of log_all_ref_updates
I like. :-)
Worthy of 1.5.0 me thinks.
--
Shawn.
-
| Jan 7, 6:05 am 2007 |
| Junio C Hamano | [PATCH] git-fetch: allow updating the current branch in a ba...
Sometimes, people have only fetch access into a bare repository
that is used as a back-up location (or a distribution point) but
does not have a push access for networking reasons, e.g. one end
being behind a firewall, and updating the "current branch" in
such a case is perfectly fine.
This allows such a fetch without --update-head-ok, which is a
flag that should never be used by end users otherwise.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
"Shawn O. Pearce" <spearce@spear...
| Jan 7, 6:19 am 2007 |
| Steven Grimm | git.git missing recent revisions?
I noticed Junio's latest "what's in git.git" message listed my two
patches, which surprised me since I do a pull at least once a day on my
git source repo and hadn't seen them show up yet.
So I did a fresh clone:
$ git-clone git://git.kernel.org/pub/scm/git/git.git/ git
$ cd git
$ git branch
* master
My changes aren't there. I looked at the headers of Junio's latest email
message to see what my head revision should be (and by the way, putting
the rev IDs there was a pretty cool idea!):
...
| Jan 7, 4:23 am 2007 |
| Eric Wong | [PATCH] git-svn: fix show-ignore
Looks like I broke it in 747fa12cef73b6ca04fffaddaad7326cf546cdea
but never noticed.
Signed-off-by: Eric Wong <normalperson@yhbt.net>
---
git-svn.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index 5377762..1da31fd 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -536,7 +536,7 @@ sub show_ignore {
my $repo;
$SVN ||= libsvn_connect($SVN_URL);
my $r = defined $_revision ? $_revision : $SVN->get_latest_revnum;
- libsvn...
| Jan 7, 2:25 am 2007 |
| previous day | today | next day |
|---|---|---|
| January 6, 2007 | January 7, 2007 | January 8, 2007 |
| Linus Torvalds | Linux 2.6.21-rc5 |
| Linus Torvalds | Linux 2.6.26-rc4 |
| Christoph Hellwig | Re: [PATCH] Version 3 (2.6.23-rc8) Smack: Simplified Mandatory Access Control Kernel |
| Bryan Woods | Stardom SATA HSM violation |
git: | |
| Linus Torvalds | People unaware of the importance of "git gc"? |
| Jan Holesovsky | [PATCH] RFC: git lazy clone proof-of-concept |
| Linus Torvalds | cleaner/better zlib sources? |
| martin f krafft | Re: Track /etc directory using Git |
| Chris | OpenBSD 4.4 installation error: write failed; file system full |
| Brian A. Seklecki | sshd_config(5) PermitRootLogin yes |
| steve szmidt | Re: The Atheros story in much fewer words |
| David Newman | setting dscp or tos bits |
| Jim Winstead Jr. | Re: Root Disk/Book Disk Compatibility |
| Jan Nicolai Langfeldt | Re: Hypenation problems under LaTeX. |
| Linus Torvalds | Re: Missing linux/delay.h??? |
| Stew Ellis | Trouble with minicom scripts |
