* Re: Simple questions on GIT usage.
From: Franck @ 2005-11-14 16:36 UTC (permalink / raw)
To: Git Mailing List; +Cc: Andreas Ericsson
In-Reply-To: <cda58cb80511140746w2f691fb8y@mail.gmail.com>
Andreas
Could you cc me when you're responding to my questions since I'm not
subscribed to the GIT mailing list for now...thanks
git-branch -d option is not documented on online documentation at:
http://www.kernel.org/pub/software/scm/git/docs/
That's why I didn't find it by my self...
Regarding the second question, your feeling is wrong. What you
described is well documented in the git tutorial. There's no "hidden"
question behind the one I posted in my first email. So the question is
still: Is there a way to get information about the working repository
? For instance if I create a branch which is not based on the current
HEAD position of master branch but instead is based on a previous
poisition of master branch. Then later I want to know how I create
this branch, how can I get this information ?
Thanks
--
Franck
^ permalink raw reply
* Libification update
From: Matthias Urlichs @ 2005-11-14 16:31 UTC (permalink / raw)
To: git
I've merged my current library-ification effort with Junio's current HEAD.
URL: http://netz.smurf.noris.de/git/git.git#libize
There's a Python interface, written using Pyrex. You can now walk object
trees natively, with Python:
>>> import git
>>> e=git.env()
>>> db=e.objdb
>>> c=db.lookup("HEAD").parent[0] # "HEAD^" will work too
>>> t=c.tree
>>> t.entries[0].name
'.gitignore'
>>> t["debian"].entries[0].name
'changelog'
>>> t[".gitignore"].data[0:5]
'/git\n'
>>> t[".gitignore"].data.readline()
'/git\n' # this will work tomorrow (I hope)
I have not implemented much beyond that; keeping the code in sync is
work, so doing more will have to wait until this gets merged.
I did play with SWIG a bit. It would have simplified interfacing
languages other than Python to git. Unfortunately, there were problems:
- refering to objects SWIG did not allocate itself is a nontrivial
exercise
- so is keeping the Python-visible namespace clean
(unless you're using C++ ... probably not something we'd want to subject
the git core to ...)
- SWIG's error reporting is *scary*.
In comparison, Pyrex mostly does the right thing.
If somebody wants to start working on a SWIG/perl/tcl/... interface
for the library, be my guest. ;-)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
Ask the person next to you.
^ permalink raw reply
* Re: Simple questions on GIT usage.
From: Randal L. Schwartz @ 2005-11-14 16:37 UTC (permalink / raw)
To: Andreas Ericsson
In-Reply-To: <4378B687.3060701@op5.se>
>>>>> "Andreas" == Andreas Ericsson <ae@op5.se> writes:
Andreas> man git-branch
Andreas> It will tell you about its -d and -D options.
It will? My manpage has no -d or -D option for git-branch.
And I've been looking for something like that too. If I want to
abandon a what-if branch, how do I make sure that the branch and all
objects are deleted?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
^ permalink raw reply
* cvsexportcommit patches
From: Kevin Geiss @ 2005-11-14 16:39 UTC (permalink / raw)
To: martin.langhoff; +Cc: git
I just created a series of small, trivial patches for the cvsexportcommit
script, which fix things like command line argument handling. I'll send them to
the list in a sec.
^ permalink raw reply
* eth
From: Kevin Geiss @ 2005-11-14 16:40 UTC (permalink / raw)
To: martin.langhoff, git
---
git-cvsexportcommit.perl | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
applies-to: e604d20cd75e71750e8316348c988ef0296b3ec5
224d4f4897ea47425aafc6d491f2a0762e683a4c
diff --git a/git-cvsexportcommit.perl b/git-cvsexportcommit.perl
index 50b041c..5bce39c 100755
--- a/git-cvsexportcommit.perl
+++ b/git-cvsexportcommit.perl
@@ -4,6 +4,7 @@ use strict;
use Getopt::Std;
use File::Temp qw(tempdir);
use Data::Dumper;
+use File::Basename qw(basename);
unless ($ENV{GIT_DIR} && -r $ENV{GIT_DIR}){
die "GIT_DIR is not defined or is unreadable";
@@ -206,8 +207,7 @@ if ($opt_c) {
}
sub usage {
print STDERR <<END;
-Usage: GIT_DIR=/path/to/.gi ${\basename $0} # fetch/update GIT from CVS
- [-h] [-p] [ parent ] commit
+Usage: GIT_DIR=/path/to/.git ${\basename $0} [-h] [-p] [-v] [-c] [ parent ] commit
END
exit(1);
}
---
0.99.9.GIT
^ permalink raw reply related
* [PATCH] git-daemon: --inetd implies --syslog
From: Andreas Ericsson @ 2005-11-14 16:41 UTC (permalink / raw)
To: git
Otherwise nothing is logged anywhere, which is a Bad Thing.
Signed-off-by: Andreas Ericsson <ae@op5.se>
---
Documentation/git-daemon.txt | 2 +-
daemon.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
applies-to: 963d67921d6f65c08d51a8c93811f03274c34703
9fac415ad7ec34c21b20b3c349872304869505df
diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
index 67c5f22..3783858 100644
--- a/Documentation/git-daemon.txt
+++ b/Documentation/git-daemon.txt
@@ -35,7 +35,7 @@ OPTIONS
do not have the 'git-daemon-export-ok' file.
--inetd::
- Have the server run as an inetd service.
+ Have the server run as an inetd service. Implies --syslog.
--port::
Listen on an alternative port.
diff --git a/daemon.c b/daemon.c
index c3f8641..50a3396 100644
--- a/daemon.c
+++ b/daemon.c
@@ -627,9 +627,9 @@ int main(int argc, char **argv)
}
if (inetd_mode) {
- fclose(stderr); //FIXME: workaround
+ log_syslog = 1;
return execute();
- } else {
- return serve(port);
}
+
+ return serve(port);
}
---
0.99.9.GIT
^ permalink raw reply related
* [PATCH 2/4] git-cvsexportcommit.perl: use getopts to get binary flags
From: Kevin Geiss @ 2005-11-14 16:41 UTC (permalink / raw)
To: martin.langhoff, git
---
git-cvsexportcommit.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
applies-to: c13592c92fc8bf74afc39ee6d40cb51814cb3e24
26c7c4b051fb251cbf88eb1d6eff63e539255cf5
diff --git a/git-cvsexportcommit.perl b/git-cvsexportcommit.perl
index 5bce39c..da7dcda 100755
--- a/git-cvsexportcommit.perl
+++ b/git-cvsexportcommit.perl
@@ -12,7 +12,7 @@ unless ($ENV{GIT_DIR} && -r $ENV{GIT_DIR
our ($opt_h, $opt_p, $opt_v, $opt_c );
-getopt('hpvc');
+getopts('hpvc');
$opt_h && usage();
---
0.99.9.GIT
^ permalink raw reply related
* [PATCH 3/4] git-cvsexportcommit.perl: exit with non-0 status if patch fails.
From: Kevin Geiss @ 2005-11-14 16:42 UTC (permalink / raw)
To: martin.langhoff; +Cc: git
---
git-cvsexportcommit.perl | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
applies-to: 7e45b599120811e135c41136fae7570af7f5437b
f615833f7dad1372b93c90814674e13800e4bd63
diff --git a/git-cvsexportcommit.perl b/git-cvsexportcommit.perl
index da7dcda..d49494a 100755
--- a/git-cvsexportcommit.perl
+++ b/git-cvsexportcommit.perl
@@ -190,7 +190,7 @@ if ($dirtypatch) {
print "NOTE: One or more hunks failed to apply cleanly.\n";
print "Resolve the conflicts and then commit using:n";
print "\n $cmd\n\n";
- exit;
+ exit(1);
}
---
0.99.9.GIT
^ permalink raw reply related
* [PATCH 4/4] git-cvsexportcommit.perl: fix typos in output
From: Kevin Geiss @ 2005-11-14 16:43 UTC (permalink / raw)
To: martin.langhoff, git
---
git-cvsexportcommit.perl | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
applies-to: 717dd9ec543f5d2d6cc4b9c0af41c2f80c615f0f
7c7460d88ef6d677ad9fa29880c2fb47e4a88d6b
diff --git a/git-cvsexportcommit.perl b/git-cvsexportcommit.perl
index d49494a..5a8c011 100755
--- a/git-cvsexportcommit.perl
+++ b/git-cvsexportcommit.perl
@@ -78,7 +78,7 @@ $opt_v && print "Applying to CVS commit
# grab the commit message
`git-cat-file commit $commit | sed -e '1,/^\$/d' > .msg`;
-$? && die "Error extraction the commit message";
+$? && die "Error extracting the commit message";
my (@afiles, @dfiles, @mfiles);
my @files = `git-diff-tree -r $parent $commit`;
@@ -188,7 +188,7 @@ my $cmd = "cvs commit -F .msg $commitfil
if ($dirtypatch) {
print "NOTE: One or more hunks failed to apply cleanly.\n";
- print "Resolve the conflicts and then commit using:n";
+ print "Resolve the conflicts and then commit using:\n";
print "\n $cmd\n\n";
exit(1);
}
---
0.99.9.GIT
^ permalink raw reply related
* [PATCH 1/1] git-cvsexportcommit.perl: Fix usage() output.
From: Kevin Geiss @ 2005-11-14 16:45 UTC (permalink / raw)
To: Kevin Geiss; +Cc: martin.langhoff, git
In-Reply-To: <20051114164047.GB9131@raven.localdomain>
---
git-cvsexportcommit.perl | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
applies-to: e604d20cd75e71750e8316348c988ef0296b3ec5
224d4f4897ea47425aafc6d491f2a0762e683a4c
diff --git a/git-cvsexportcommit.perl b/git-cvsexportcommit.perl
index 50b041c..5bce39c 100755
--- a/git-cvsexportcommit.perl
+++ b/git-cvsexportcommit.perl
@@ -4,6 +4,7 @@ use strict;
use Getopt::Std;
use File::Temp qw(tempdir);
use Data::Dumper;
+use File::Basename qw(basename);
unless ($ENV{GIT_DIR} && -r $ENV{GIT_DIR}){
die "GIT_DIR is not defined or is unreadable";
@@ -206,8 +207,7 @@ if ($opt_c) {
}
sub usage {
print STDERR <<END;
-Usage: GIT_DIR=/path/to/.gi ${\basename $0} # fetch/update GIT from CVS
- [-h] [-p] [ parent ] commit
+Usage: GIT_DIR=/path/to/.git ${\basename $0} [-h] [-p] [-v] [-c] [ parent ] commit
END
exit(1);
}
---
0.99.9.GIT
^ permalink raw reply related
* Re: eth
From: Kevin Geiss @ 2005-11-14 16:47 UTC (permalink / raw)
To: Kevin Geiss; +Cc: martin.langhoff, git
In-Reply-To: <20051114164047.GB9131@raven.localdomain>
oops, I munged up the subject on this one. I resent it with '1/1' in the subject. :(
On Mon, Nov 14, 2005 at 09:40:47AM -0700, Kevin Geiss wrote:
^ permalink raw reply
* [PATCH 0/4] StGIT minor clean ups
From: Chuck Lever @ 2005-11-14 16:50 UTC (permalink / raw)
To: git
A few minor typos and additional error checking.
-- Chuck Lever
--
corporate: <cel at netapp dot com>
personal: <chucklever at bigfoot dot com>
^ permalink raw reply
* [PATCH 1/4] Better error message when renaming patches to same name
From: Chuck Lever @ 2005-11-14 16:50 UTC (permalink / raw)
To: git
In-Reply-To: <20051114165007.22202.69803.stgit@dexter.citi.umich.edu>
Generate a more precise error message when trying to rename a patch to the
same name. This is what we get currently:
[cel@dexter main]$ stg rename nfs_direct_wait nfs_direct_wait
Renaming patch "nfs_direct_wait" -> "nfs_direct_wait"...stg rename: Patch
"nfs_direct_wait" already exists
[cel@dexter main]$
Signed-off-by: Chuck Lever <cel@netapp.com>
---
stgit/stack.py | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/stgit/stack.py b/stgit/stack.py
index 1ffeaee..0907b37 100644
--- a/stgit/stack.py
+++ b/stgit/stack.py
@@ -775,6 +775,9 @@ class Series:
applied = self.get_applied()
unapplied = self.get_unapplied()
+ if oldname == newname:
+ raise StackException, '"To" name and "from" name are the same'
+
if newname in applied or newname in unapplied:
raise StackException, 'Patch "%s" already exists' % newname
^ permalink raw reply related
* [PATCH 3/4] Fix a typo in "stg pick"
From: Chuck Lever @ 2005-11-14 16:50 UTC (permalink / raw)
To: git
In-Reply-To: <20051114165007.22202.69803.stgit@dexter.citi.umich.edu>
"Unknown" is misspelled.
Signed-off-by: Chuck Lever <cel@netapp.com>
---
stgit/commands/pick.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/stgit/commands/pick.py b/stgit/commands/pick.py
index 3c52a49..c01c799 100644
--- a/stgit/commands/pick.py
+++ b/stgit/commands/pick.py
@@ -64,7 +64,7 @@ def func(parser, options, args):
elif len(patch_branch) == 2:
patch = patch_branch[0]
else:
- raise CmdException, 'Unkown patch name'
+ raise CmdException, 'Unknown patch name'
commit_id = git_id(commit_str)
commit = git.Commit(commit_id)
^ permalink raw reply related
* [PATCH 2/4] use "crt_series.get_branch()" instead of "git.get_head_file()"
From: Chuck Lever @ 2005-11-14 16:50 UTC (permalink / raw)
To: git
In-Reply-To: <20051114165007.22202.69803.stgit@dexter.citi.umich.edu>
More cleanup to the branch command.
Signed-off-by: Chuck Lever <cel@netapp.com>
---
stgit/commands/branch.py | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/stgit/commands/branch.py b/stgit/commands/branch.py
index d85ba69..9bf6cdb 100644
--- a/stgit/commands/branch.py
+++ b/stgit/commands/branch.py
@@ -147,7 +147,7 @@ def func(parser, options, args):
elif options.protect:
if len(args) == 0:
- branch_name = git.get_head_file()
+ branch_name = crt_series.get_branch()
elif len(args) == 1:
branch_name = args[0]
else:
@@ -182,7 +182,7 @@ def func(parser, options, args):
elif options.unprotect:
if len(args) == 0:
- branch_name = git.get_head_file()
+ branch_name = crt_series.get_branch()
elif len(args) == 1:
branch_name = args[0]
else:
@@ -222,4 +222,4 @@ def func(parser, options, args):
if len(args) != 0:
parser.error('incorrect number of arguments')
- print git.get_head_file()
+ print crt_series.get_branch()
^ permalink raw reply related
* [PATCH 4/4] Fix a typo in the "add" command's documentation
From: Chuck Lever @ 2005-11-14 16:51 UTC (permalink / raw)
To: git
In-Reply-To: <20051114165007.22202.69803.stgit@dexter.citi.umich.edu>
Signed-off-by: J. Bruce Fields <bfields@fieldses.org>
Signed-off-by: Chuck Lever <cel@netapp.com>
---
stgit/commands/add.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/stgit/commands/add.py b/stgit/commands/add.py
index 999ce2b..fc9c5a7 100644
--- a/stgit/commands/add.py
+++ b/stgit/commands/add.py
@@ -27,7 +27,7 @@ from stgit import stack, git
help = 'add files or directories to the repository'
usage = """%prog [options] <files/dirs...>
-Add a the files or directories passed as arguments to the
+Add the files or directories passed as arguments to the
repository. When a directory name is given, all the files and
subdirectories are recursively added."""
^ permalink raw reply related
* [PATCH] git-branch: Mention -d and -D in man-page.
From: Andreas Ericsson @ 2005-11-14 16:53 UTC (permalink / raw)
To: git
Signed-off-by: Andreas Ericsson <ae@op5.se>
---
Documentation/git-branch.txt | 15 +++++++++++----
1 files changed, 11 insertions(+), 4 deletions(-)
applies-to: 963d67921d6f65c08d51a8c93811f03274c34703
f67747f6501aa0b8bd5e58a3933fd1a738f69441
diff --git a/Documentation/git-branch.txt b/Documentation/git-branch.txt
index a7121a4..98014f6 100644
--- a/Documentation/git-branch.txt
+++ b/Documentation/git-branch.txt
@@ -3,11 +3,11 @@ git-branch(1)
NAME
----
-git-branch - Create a new branch.
+git-branch - Create a new branch, or remove an old one.
SYNOPSIS
--------
-'git-branch' [<branchname> [start-point]]
+'git-branch' [-d | -D] [<branchname> [start-point]]
DESCRIPTION
-----------
@@ -19,11 +19,18 @@ created, otherwise it will be created at
OPTIONS
-------
+-d::
+ Delete a branch. The branch must be fully merged.
+
+-D::
+ Delete a branch irrespective of its index status.
+
<branchname>::
- The name of the branch to create.
+ The name of the branch to create or delete.
start-point::
- Where to create the branch; defaults to HEAD.
+ Where to create the branch; defaults to HEAD. This
+ option has no meaning with -d and -D.
Author
------
---
0.99.9.GIT
^ permalink raw reply related
* Re: Simple questions on GIT usage.
From: Andreas Ericsson @ 2005-11-14 16:56 UTC (permalink / raw)
To: Randal L. Schwartz; +Cc: Git Mailing List
In-Reply-To: <86iruvxk1i.fsf@blue.stonehenge.com>
Randal L. Schwartz wrote:
>>>>>>"Andreas" == Andreas Ericsson <ae@op5.se> writes:
>
>
> Andreas> man git-branch
>
> Andreas> It will tell you about its -d and -D options.
>
> It will? My manpage has no -d or -D option for git-branch.
>
Ah. It's the help output that has them. I've submitted a patch to add
them to the man-page though, so it should show up soonish.
> And I've been looking for something like that too. If I want to
> abandon a what-if branch, how do I make sure that the branch and all
> objects are deleted?
>
git branch -D branchname
git prune
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
^ permalink raw reply
* Re: ./configure script prototype
From: Chris Wedgwood @ 2005-11-14 17:45 UTC (permalink / raw)
To: Andreas Ericsson; +Cc: Git Mailing List
In-Reply-To: <4378B74E.2060208@op5.se>
On Mon, Nov 14, 2005 at 05:11:58PM +0100, Andreas Ericsson wrote:
> Ach no. The configure script really needs to be portable. POSIX (or
> SUS or some such) define a minimum syntax that any shell must
> support when invoked as /bin/sh.
Then bashism need to go away and it should be test with
dash/ash/whatever.
^ permalink raw reply
* Fix git-rev-list "date order" with --topo-order
From: Linus Torvalds @ 2005-11-14 18:01 UTC (permalink / raw)
To: Matthias Urlichs, Junio C Hamano; +Cc: Git Mailing List
In-Reply-To: <pan.2005.11.14.04.36.38.784541@smurf.noris.de>
This fixes git-rev-list so that when there are multiple branches, we still
sort the heads in proper approximate date order even when sorting the
output topologically.
This makes things like
gitk --all -d
work sanely and show the branches in date order (where "date order" is
obviously modified by the paren-child dependency requirements of the
topological sort).
The trivial fix is to just build the "work" list in date order rather than
inserting the new work entries at the beginning.
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
---
This should also fix this report, although Matthias should double-test..
On Mon, 14 Nov 2005, Matthias Urlichs wrote:
>
> > $ gitk $(cd .git/lost+found/commit && echo ??*)
>
> Along those lines... I just tried that, it found a whole heap of old
> commits I didn't yet clean up, and they're sorted by their SHA1.
>
> In other words, actually finding the latest commit in there was a
> nontrivial task.
>
> I don't speak tcl, so could somebody please change "gitk -d" to sort its
> command line by date (newest first, of course)? Thanks.
diff --git a/commit.c b/commit.c
index 534c03e..ebf4db6 100644
--- a/commit.c
+++ b/commit.c
@@ -536,7 +536,7 @@ int count_parents(struct commit * commit
void sort_in_topological_order(struct commit_list ** list)
{
struct commit_list * next = *list;
- struct commit_list * work = NULL;
+ struct commit_list * work = NULL, **insert;
struct commit_list ** pptr = list;
struct sort_node * nodes;
struct sort_node * next_nodes;
@@ -580,11 +580,12 @@ void sort_in_topological_order(struct co
* the tips serve as a starting set for the work queue.
*/
next=*list;
+ insert = &work;
while (next) {
struct sort_node * node = (struct sort_node *)next->item->object.util;
if (node->indegree == 0) {
- commit_list_insert(next->item, &work);
+ insert = &commit_list_insert(next->item, insert)->next;
}
next=next->next;
}
^ permalink raw reply related
* Re: ./configure script prototype
From: Joel Becker @ 2005-11-14 18:19 UTC (permalink / raw)
To: Petr Baudis; +Cc: Andreas Ericsson, Git Mailing List
In-Reply-To: <20051114132956.GT30496@pasky.or.cz>
On Mon, Nov 14, 2005 at 02:29:56PM +0100, Petr Baudis wrote:
> Dear diary, on Mon, Nov 14, 2005 at 01:18:52PM CET, I got a letter
> where Andreas Ericsson <ae@op5.se> said that...
> > --prefix=*)
> > prefix=${1##*=}
${i# and ${i% are POSIX, iirc.
Joel
--
Life's Little Instruction Book #197
"Don't forget, a person's greatest emotional need is to
feel appreciated."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
^ permalink raw reply
* [Question] info/grafts file.
From: Carl Baldwin @ 2005-11-14 18:20 UTC (permalink / raw)
To: git
Greetings,
A simple question to clarify something in the repository.
What level of support is to be expected for the .git/info/grafts file?
I added a grafts file to a repository imported from SVN. However, when
I cloned the repository using git clone -l -s I did not end up with a
grafts file in the cloned repository.
Cheers,
Carl
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Carl Baldwin Systems VLSI Laboratory
Hewlett Packard Company
MS 88 work: 970 898-1523
3404 E. Harmony Rd. work: Carl.N.Baldwin@hp.com
Fort Collins, CO 80525 home: Carl@ecBaldwin.net
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
^ permalink raw reply
* Offtopic [Re: Can't use gitk.]
From: Linus Torvalds @ 2005-11-14 18:24 UTC (permalink / raw)
To: Franck; +Cc: Andreas Ericsson, Git Mailing List
In-Reply-To: <cda58cb80511140355q1add0ba5n@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 758 bytes --]
On Mon, 14 Nov 2005, Franck wrote:
>
> oops, sorry Andreas for that ! I use to spelling this name without 's'
> that's why I did the mistake I think.
In Finland and Sweden Andrea without the "s" is a girls name, while
Andreas with the "s" (or André without "-as") is a boy.
It's not even very rare. "Andrea" was the 84th most popular female name in
Sweden in 2000.
It can be confusing, since in Italy (and, I think, southern Germany and
much of Eastern Europe), "Andrea" is a boy, and in fact, the name
originally comes from the Greek meaning "man".
In the rest of the world, Andrea seems to mostly female, but it probably
depends on where the cultural influences come from.
So leaving off the "s" can be very strange to the recipient.
Linus
^ permalink raw reply
* [RFC] Not grabbing ALL branches and tags with git clone
From: Carl Baldwin @ 2005-11-14 18:26 UTC (permalink / raw)
To: git
Greetings,
Lately, I've found that 'git clone' gives me more than what I want.
Especially when there are a lot of branches and tags in the remote
repository.
I have found myself doing something like the following in most cases.
% mkdir work && cd work
% git init-db
% git fetch <url> <refspec>
% git checkout -f -b master <branch>
Usually, I will use a file in .git/remotes but you get the idea. I was
thinking that it might make sense to make git clone able to do this.
Change the usage of git clone so that it looks like this:
git clone [-l [-s]] [-q] [-u <upload-pack>] [-n] <repo> <dir> [<refspec>] ...
git clone would behave exactly the same way if no refspec were given but
if a refspec (or multiple refspecs) were given on the command line then
git clone would behave more like my series of three commands above.
I haven't looked at what it would take to patch git clone for this
purpose. Just wanted to see what you thought.
Cheers,
Carl
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Carl Baldwin Systems VLSI Laboratory
Hewlett Packard Company
MS 88 work: 970 898-1523
3404 E. Harmony Rd. work: Carl.N.Baldwin@hp.com
Fort Collins, CO 80525 home: Carl@ecBaldwin.net
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
^ permalink raw reply
* Re: ./configure script prototype
From: Linus Torvalds @ 2005-11-14 18:39 UTC (permalink / raw)
To: Joel Becker; +Cc: Petr Baudis, Andreas Ericsson, Git Mailing List
In-Reply-To: <20051114181958.GD20749@ca-server1.us.oracle.com>
On Mon, 14 Nov 2005, Joel Becker wrote:
> On Mon, Nov 14, 2005 at 02:29:56PM +0100, Petr Baudis wrote:
> > Dear diary, on Mon, Nov 14, 2005 at 01:18:52PM CET, I got a letter
> > where Andreas Ericsson <ae@op5.se> said that...
> > > --prefix=*)
> > > prefix=${1##*=}
>
> ${i# and ${i% are POSIX, iirc.
They may be in POSIX, but they sure as h*ll aren't portable.
There's a _lot_ of machines out there that don't do POSIX, just because
those "newfangled" things are so complicated.
Also, even in POSIX, there's tons of different substandards, and you might
follow one but not the other.
Finally, even if somebody is certified, they can very well be certified
with "exceptions", so if they claim POSIX it doesn't necessarily mean that
they follow all of it.
If you want to do a "configure" script (and I'm not sure it's worth it),
you should cater to the lowest common denominator for it to be meaningful.
What the hell that would be, I have no idea, since if you ever want to run
on native Windows, it won't even be traditional shell. But traditional
shell is at least a lot closer to that lowest common denominator than
POSIX shell is.
That said, most of those ${var...} sequences definitely _are_ very
traditional, and for all I know, ## may be too.
Linus
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox