Kalle Olavi Niemitalo k...@iki.fi writes:
and neither process blocked any signals (not even SIGCHLD as system(3)
would).
If you don't have a SIGCHLD handler it won't matter anyway.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5
On 11/11/2012 01:58 AM, Felipe Contreras wrote:
It doesn't seem like zsh listens to that variable in sh mode:
$ zsh -c 'emulate sh; NULLCMD=foobar; content'
Right; emulate sh by itself is probably enough today (autoconf, trying
to make its generated scripts extra-portable, tends to
Patterns beginning with a slash are converted to Windows paths before
test-wildmatch gets to see them. Avoid this case by always writing
XXX/abc instead of /abc. The leading XXX will be removed by
test-wildmatch itself before processing.
Any patterns beginning with a forward slash is rejected by
Character class xdigit is the only one that hits 6 character limit
defined by CHAR_CLASS_MAX_LENGTH. All other character classes are 5
character long and therefore never caught by this.
This should make xdigit tests in t3070 pass on Windows.
Reported-by: Johannes Sixt j...@kdbg.org
.gitattributes pattern syntax is supposed to be the same as .gitignore
(except a few things that do not make sense in attr context, but
that's a different issue). .gitignore uses fnmatch() as the matching
machinery and \ is accepted as an escape code. In theory the pattern
'foo\ bar' should match
W. Trevor King wk...@tremily.us writes:
On Thu, Nov 08, 2012 at 11:34:54PM -0800, Junio C Hamano wrote:
I would not object to git config submodule.$name.branch $value, on
the other hand. git config can be used to set a piece of data
that has specific meaning, but as a low-level tool, it is
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Patterns beginning with a slash are converted to Windows paths before
test-wildmatch gets to see them. Avoid this case by always writing
XXX/abc instead of /abc. The leading XXX will be removed by
test-wildmatch itself before processing.
Any
Jason Timrod wrote:
I'm looking for a way to make the -sb options to git-status the default
somehow.
I've aliased `git status` to `git status -sb` too, and I think it's a
very sensible default; who wants to see
# Changes not staged for commit:
# (use git add file... to update what will
Hi,
On Sun, Nov 11, 2012 at 2:13 AM, Thiago Farina tfrans...@gmail.com wrote:
On Sat, Nov 10, 2012 at 9:40 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
On Sun, Nov 11, 2012 at 12:19 AM, Deniz Türkoglu de...@spotify.com wrote:
This is my first mail to the git mailing list. I have
On Mon, Oct 29, 2012 at 8:56 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
On Sun, Oct 28, 2012 at 10:34 PM, Andreas Schwab sch...@linux-m68k.org
wrote:
Geert Uytterhoeven ge...@linux-m68k.org writes:
Is there a way to force removing unreachable objects in the presence of
broken
Hi Peff,
Jeff King wrote:
An off-list discussion made me wonder if something like this would be
useful:
git log -p --submodule=log:' %m %an %ae: %s'
where the format could be whatever you find useful.
Interesting. Don't you mean `git diff` in place of `git log -p`
though? I don't
Hi,
I note that when defining a .mailmap file, that it's honoured by git-shotlog(1)
by default, but for git-log(1) I have to define an entirely new --pretty=
formatting option to use it.
Why is this? Why doesn't git-log honour this by default like git-shortlog does?
Would there be a way of
On Sun, Nov 11, 2012 at 2:13 AM, Thiago Farina tfrans...@gmail.com wrote:
On Sat, Nov 10, 2012 at 9:40 PM, Felipe Contreras
Personally I think reviews on the mailing list is far superior than
any other review methods. I've even blogged about it and all the
reasons[1]. Gerrit is better than
On Sun, Nov 11, 2012 at 2:28 AM, Deniz Türkoglu de...@spotify.com wrote:
On Sat, Nov 10, 2012 at 3:40 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
On Sun, Nov 11, 2012 at 12:19 AM, Deniz Türkoglu de...@spotify.com wrote:
This is my first mail to the git mailing list. I have been
On Sat, Nov 10, 2012 at 8:25 PM, A Large Angry SCM gitzi...@gmail.com wrote:
On 11/10/2012 01:43 PM, Felipe Contreras wrote:
So, the options are:
a) Leave the name conversion to the export tools, and when they miss
some weird corner case, like 'Authoremail', let the user face the
Felipe Contreras wrote:
On Sun, Nov 11, 2012 at 11:32 AM, Ramkumar Ramachandra
artag...@gmail.com wrote:
I'm experiencing test failures in contrib/remote-helpers.
Which are your versions of hg, and bzr?
Mercurial Distributed SCM (version 1.9.1)
Bazaar (bzr) 2.4.1
Ram
--
To unsubscribe from
Felipe Contreras wrote:
On Sun, Nov 11, 2012 at 11:41 AM, Ramkumar Ramachandra
artag...@gmail.com wrote:
test-hg.sh forgets to set ui.username, which is required for `hg
commit`. Fix this.
Hmm, I get 'no username found, using 'felipec@nysa' instead', but
everything works fine.
I get:
Hi again,
Ramkumar Ramachandra wrote:
Don't you mean `git diff` in place of `git log -p`
though? I don't think `git log --submodule` does anything differently
from `git log`.
Sorry for the nonsense. I just realized that it affects the diffs
shown by `git log -p`.
Ram
--
To unsubscribe from
On Sun, Nov 11, 2012 at 10:14 AM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Requiring everyone to use a web browser would limit the amount of ways
people can review patches.
I don't see that as a limitation as I think everyone has access to a
web browser these days, don't have?
How
On Sun, Nov 11, 2012 at 2:09 PM, Thiago Farina tfrans...@gmail.com wrote:
On Sun, Nov 11, 2012 at 10:14 AM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Requiring everyone to use a web browser would limit the amount of ways
people can review patches.
I don't see that as a limitation as
This script is not really exercising the remote-helper functionality,
but more the python framework for remote helpers that live in
git_remote_helpers.
It's also not a good example of how to write remote-helpers, unless you
are planning to use python, and even then you might not want to use this
The rest of the code uses ' Z$'. Lets use that for
test_completion_long() as well.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
t/t9902-completion.sh | 27 +--
1 file changed, 13 insertions(+), 14 deletions(-)
diff --git a/t/t9902-completion.sh
Lots of duplicated code!
No functional changes.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
t/t9902-completion.sh | 76 ++-
1 file changed, 27 insertions(+), 49 deletions(-)
diff --git a/t/t9902-completion.sh
By using print_comp as suggested by SZEDER Gábor.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
t/t9902-completion.sh | 15 +--
1 file changed, 5 insertions(+), 10 deletions(-)
diff --git a/t/t9902-completion.sh b/t/t9902-completion.sh
index 66c7af6..9b38b69 100755
For repositories it is possible to maintain a README.html which will
be shown on the summary page. This is not possible for the server
root.
German law requires to provide contact data on the web server. This
data could easily be entered in the overview page using a README.html.
Furthermore it
On 11.11.12 14:59, Felipe Contreras wrote:
test_expect_success 'test biridectionality' '
+ echo -n marks-cur
+ echo -n marks-new
Unless I messed up the patch:
Minor issue: still a typo biridectionality
Major issue: echo -n is still not portable.
Could we simply use
touch
Hi,
Am 06.10.2012 20:28 schrieb Junio C Hamano:
It is either that it was simply forgotten, or after I wrote the part
you quoted early in January there were discussions later that showed
the patch was not desirable for some reason. I do not recall which.
I noticed no threads about possible
git-svn reads passwords from an interactive terminal or by using
GIT_ASKPASS helper tool. But if GIT_ASKPASS environment variable is not
set, git-svn does not try to use SSH_ASKPASS as git-core does. This
cause GUIs (w/o STDIN connected) to hang waiting forever for git-svn to
complete
On Sun, Nov 11, 2012 at 05:46:32PM +0100, René Scharfe wrote:
However, I couldn't reproduce it on Linux : where the windows
implementations crashes at a ~32000 depth (*not* exactly 32768, mind
you), on linux it happily went through 10 commits. I didn't take
time to look much further, but
The launch_editor function uses the convenient run_command_*
interface. Let's use the more flexible start_command and
finish_command functions, which will let us manipulate the
parent state while we're waiting for the child to finish.
Signed-off-by: Jeff King p...@peff.net
---
editor.c | 10
git-svn reads usernames and other user queries from an interactive
terminal. This cause GUIs (w/o STDIN connected) to hang waiting forever
for git-svn to complete
(http://code.google.com/p/tortoisegit/issues/detail?id=967).
This change extends the Git::prompt helper, so that it can also be used
SIGINT is not generally an interesting signal to the user,
since it is typically caused by them hitting ^C or
otherwise telling their terminal to send the signal.
Signed-off-by: Jeff King p...@peff.net
---
I thought about making this an optional parameter for run-command, but
it seems like
We block SIGINT while the editor runs so that git is not
killed accidentally by a stray ^C meant for the editor or
its subprocesses. This works because most editors ignore
SIGINT.
However, some editor wrappers, like emacsclient, expect to
die due to ^C. We detect the signal death in the editor
From: Paul Fox p...@foxharp.boston.ma.us
The user's editor likely catches SIGINT (ctrl-C). but if
the user spawns a command from the editor and uses ctrl-C to
kill that command, the SIGINT will likely also kill git
itself (depending on the editor, this can leave the terminal
in an unusable
v1 is here:
http://mid.gmane.org/1349196670-2844-1-git-send-email-artag...@gmail.com
v2 is here:
http://mid.gmane.org/1351766630-4837-1-git-send-email-artag...@gmail.com
This version was prepared in response to Peff's review of v2. As
suggested, I've created a separate function which both
19299a8 (Documentation: Move diff.driver.* from config.txt to
diff-config.txt, 2011-04-07) moved the diff configuration options to
diff-config.txt, but forgot about diff.wordRegex, which was left
behind in config.txt. Fix this.
Signed-off-by: Ramkumar Ramachandra artag...@gmail.com
---
Introduce a diff.submodule configuration variable corresponding to the
'--submodule' command-line option of 'git diff'.
Signed-off-by: Ramkumar Ramachandra artag...@gmail.com
---
Documentation/diff-config.txt|7 ++
Documentation/diff-options.txt |3 +-
cache.h
On 11/11/2012 07:41 AM, Felipe Contreras wrote:
On Sat, Nov 10, 2012 at 8:25 PM, A Large Angry SCMgitzi...@gmail.com wrote:
On 11/10/2012 01:43 PM, Felipe Contreras wrote:
So, the options are:
a) Leave the name conversion to the export tools, and when they miss
some weird corner case, like
If we pass the full command to run, we should be able to use it in more
extensible ways--see next patch.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
git-send-email.perl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/git-send-email.perl
cc-cmd is only per-file, and many times receipients get lost without
seing the full patch series.
So, add an option for series-cc-cmd, which receives as an argument
rev-list options, just like format-patch.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
There's no point in asking this over and over if the user already
properly configured his/her name and email.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
I got really tired of 'git send-email' always asking me from which address to
send mails... that's already configured.
You can run it like format-patch:
% git cc-cmd master..my-branch
And you'll get relevant people to Cc.
The code finds the changes in each commit in the list, runs 'git blame'
to see which other commits are relevant to those lines, and then adds
the author and signer to the list.
Finally, it
On Sun, Nov 11, 2012 at 12:00:44PM -0500, A Large Angry SCM wrote:
a) Leave the name conversion to the export tools, and when they miss
some weird corner case, like 'Authoremail', let the user face the
consequences, perhaps after an hour of the process.
[...]
b) Do the name conversion in
On Sun, Nov 11, 2012 at 06:45:32PM +0100, Felipe Contreras wrote:
If there is a standard filter, then what is the advantage in doing it as
a pipe? Why not just teach fast-import the same trick (and possibly make
it optional)? That would be simpler, more efficient, and it would make
it
jeff wrote:
On Sun, Nov 11, 2012 at 10:48:46AM -0500, Jeff King wrote:
Silly me. When I thought through the impact of Paul's patch, I knew that
we would notice signal death of the editor. But I totally forgot to
consider that the blocked signal is inherited by the child process. I
On Sun, Nov 11, 2012 at 01:09:02PM -0500, Jason Pyeron wrote:
My google fu has failed me on this issue. I am trying to setup http(s)
repositories for git. If I require authenticated users then git asks
for a username and password for the first volley of communications, but
then does not
On Sun, Nov 11, 2012 at 7:14 PM, Jeff King p...@peff.net wrote:
On Sun, Nov 11, 2012 at 06:45:32PM +0100, Felipe Contreras wrote:
If there is a standard filter, then what is the advantage in doing it as
a pipe? Why not just teach fast-import the same trick (and possibly make
it optional)?
On Sun, Nov 11, 2012 at 1:48 PM, Ramkumar Ramachandra
artag...@gmail.com wrote:
Felipe Contreras wrote:
On Sun, Nov 11, 2012 at 11:32 AM, Ramkumar Ramachandra
artag...@gmail.com wrote:
I'm experiencing test failures in contrib/remote-helpers.
Which are your versions of hg, and bzr?
krzysztof wrote:
On Sun, Nov 11, 2012 at 11:31:00AM -0500, Jeff King wrote:
Here's a series that I think should resolve the situation for everybody.
[1/5]: launch_editor: refactor to use start/finish_command
The cleanup I sent out a few minutes ago.
[2/5]:
On Sun, Nov 11, 2012 at 03:24:19PM -0500, Paul Fox wrote:
krzysztof wrote:
Looks ok, but what about SIGQUIT? Some editors like GNU ed (0.4 and 1.6)
ignore SIGQUIT, and after SIGQUIT git dies, but editor is still running.
After pressing any key ed receives -EIO and prints stdin:
On 11.11.2012, at 14:59, Felipe Contreras wrote:
People seeking for reference would find it useful.
Hm, I don't understand this commit message. Probably means I am just too dumb,
but since I am one of those people who would likely be seeking for reference, I
would really appreciate if it
On 11.11.2012, at 14:59, Felipe Contreras wrote:
Basically this is what we want:
== pull ==
testgit transport-helper
* export - import
# testgit.marks git.marks
== push ==
testgit transport-helper
On 11.11.2012, at 14:59, Felipe Contreras wrote:
It's way simpler. It exerceises the same features of remote helpers.
Typo: exerceises = exercises
Cheers,
Max
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo
On 11.11.2012, at 14:59, Felipe Contreras wrote:
When an object has already been exported (and thus is in the marks) it's
flagged as SHOWN, so it will not be exported again, even if in a later
time it's exported through a different ref.
We don't need the object to be exported again, but we
On Sun, Nov 11, 2012 at 9:49 PM, Max Horn m...@quendi.de wrote:
On 11.11.2012, at 14:59, Felipe Contreras wrote:
People seeking for reference would find it useful.
Hm, I don't understand this commit message. Probably means I am j git
fast-export --use-done-featureust too dumb, but since I
Krzysztof Mazur krzys...@podlesie.net writes:
That's why I'm proposing in case of SIGQUIT just killing the editor
(SIGTERM is sufficient for ed).
So git will ignore SIGINT, but die on SIGQUIT (and kill editor
that ignores SIGQUIT).
system(3) also ignores SIGQUIT.
Andreas.
--
Andreas
Felipe Contreras felipe.contre...@gmail.com writes:
Implemented now. I'm not handling the 'tip' revision, but most likely
it's also the '.' revision. In this case a fake 'master' bookmark will
be created to track that revision.
Hi Felipe. Sorry for the slow response, I've been snowed under
Support for the p4 move command was added in 8e9497c (git p4:
add support for 'p4 move' in P4Submit, 2012-07-12), which checks
to make sure the client and server support the command.
But older versions of p4d may not handle the -k argument, and
newer p4d allow disabling p4 move with a
Hi,
It was asked recently whether git status could output the short-form instead
of the long output (via its -sb options). To that end, I've created a
rough POC on how this might look. It's deliberately lacking documentation;
I was curious to know whether:
status.shortwithbranch = true
Was
It is currently not possible to use the short-form output of git status
without declaring an alias to do so.
This isn't always desirable therfore, define a git config option which can
be set to display the short-form: status.shortwithbranch
Signed-off-by: Thomas Adam tho...@xteddy.org
---
Hi,
On Sun, 11 Nov 2012, Jeff King wrote:
On Sun, Nov 11, 2012 at 05:46:32PM +0100, René Scharfe wrote:
However, I couldn't reproduce it on Linux : where the windows
implementations crashes at a ~32000 depth (*not* exactly 32768, mind
you), on linux it happily went through 10
The cygwin project recently switched to a new implementation of the
windows api, now using header files from the mingw-64 project. These
new header files are incompatible with the way cygwin.c included the
old headers: cygwin.c can be compiled using the new or the older (mingw)
headers, but
I understand from the feedback that gerrit should get better on making
it possible to review code via e-mail, as pointed out in Nguyen's
mail, a flow like Shawn mentioned[1] can be a good solution.
FWIW, I can fetch the change(s) from gerrit I am interested in and
review it any time I want. I
On Sun, 11 Nov 2012, Deniz Türkoglu wrote:
I understand from the feedback that gerrit should get better on making
it possible to review code via e-mail, as pointed out in Nguyen's
mail, a flow like Shawn mentioned[1] can be a good solution.
FWIW, I can fetch the change(s) from gerrit I am
Their webserver seems to be configured quite restrictively
(eg. cannot access files like 'packed-refs').
Probably it just doesn't exist.
Aren' these files requied ?
cu
--
Mit freundlichen Grüßen / Kind regards
Enrico Weigelt
VNC - Virtual Network Consult GmbH
Head Of Development
I am physically back but still am far from catching up with the list
traffic (yet). After skimming my inbox, it appears that you have
done a magnificent job keeping track of topics in flight and merging
low-risk fixes early to the 'master' branch.
I am hoping that I can ask you to do another
On Sun, Nov 11, 2012 at 07:12:26PM -0800, Junio C Hamano wrote:
I am physically back but still am far from catching up with the list
traffic (yet). After skimming my inbox, it appears that you have
done a magnificent job keeping track of topics in flight and merging
low-risk fixes early to
Minor changes since from v2 set. Reposting primarily because I mucked
up the Cc: list (again) and hoping to route feedback to the appropriate
audience.
This patch set can be divided into two sets:
1. Provide useful advice for rejected tag references.
push: return reject reasons via a
Pass all rejection reasons back from transport_push(). The logic is
simpler and more flexible with regard to providing useful feedback.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
builtin/push.c | 13 -
builtin/send-pack.c | 4 ++--
transport.c | 17
Advising the user to fetch and merge only makes sense if the rejected
reference is a branch. If none of the rejections were for branches,
tell the user they need to force the update(s).
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
builtin/push.c | 16 ++--
cache.h| 1
If the reference exists on the remote and the the update is not a
delete, then mark as an update. This is in preparation for handling
tags and branches differently when pushing.
Signed-off-by: Chris Rorvick ch...@rorvick.com
---
cache.h | 1 +
remote.c | 18 +++---
2 files
References are allowed to update from one commit-ish to another if the
former is a ancestor of the latter. This behavior is oriented to
branches which are expected to move with commits. Tag references are
expected to be static in a repository, though, thus an update to a
tag (lightweight and
Add a flag for indicating an update to a reference requires force.
Currently the nonfastforward flag of a ref is used for this when
generating status the status message. A separate flag insulates the
status logic from the details of set_ref_status_for_push().
Signed-off-by: Chris Rorvick
Enrico Weigelt enrico.weig...@vnc.biz writes:
Their webserver seems to be configured quite restrictively
(eg. cannot access files like 'packed-refs').
Probably it just doesn't exist.
Aren' these files requied ?
No. If you've never run git pack-refs it's never created.
Andreas.
--
74 matches
Mail list logo
