From: Johannes Sixt j...@kdbg.org
The test case depends on that test-sigchain can commit suicide by a call
to raise(SIGTERM) in a way that run-command.c::wait_or_whine() can detect
as death through a signal. There are no POSIX signals on Windows, and a
sufficiently close emulation is not
On Thu, Jun 06, 2013 at 08:34:41AM +0200, Johannes Sixt wrote:
From: Johannes Sixt j...@kdbg.org
The test case depends on that test-sigchain can commit suicide by a call
to raise(SIGTERM) in a way that run-command.c::wait_or_whine() can detect
as death through a signal. There are no POSIX
On Thu, Jun 6, 2013 at 1:44 AM, Jeff King p...@peff.net wrote:
On Thu, Jun 06, 2013 at 01:41:05AM -0500, Felipe Contreras wrote:
Thanks. I wasn't quite clear on how the signal handling worked on
Windows, but from your description, I agree there is not any point in
running the test at all.
On 5 June 2013 16:45, Felipe Contreras felipe.contre...@gmail.com wrote:
On Tue, Jun 4, 2013 at 7:04 PM, Junio C Hamano gits...@pobox.com wrote:
That might make sense for the shorter term, but in longer term I see
Perl as declining in favor of other languages. It's only a matter of
time before
On Thu, Jun 6, 2013 at 2:26 AM, demerphq demer...@gmail.com wrote:
On 5 June 2013 16:45, Felipe Contreras felipe.contre...@gmail.com wrote:
On Tue, Jun 4, 2013 at 7:04 PM, Junio C Hamano gits...@pobox.com wrote:
That might make sense for the shorter term, but in longer term I see
Perl as
On 06/06/2013 12:40 AM, Jeff King wrote:
We cannot create an archive from a blob object, so we would
not expect anyone to provide one to us. And if they do, we
will fail anyway just after the reachability check. We can
therefore optimize our reachability check to ignore blobs
completely, and
On Mac OS X, any application that is started from the Terminal will open
behind all running applications; as a work-around, manually bring ourselves
to the front. (Stolen from gitk, commit 76bf6ff93e.)
We do this as the very first thing, so that any message boxes that might pop
up during the rest
Hey,
What I want to do:
* ignore certain patterns completely
* but keep one important directoy
* but not the patterns from the first step that are located within
that directory.
Concrete example: I'm tracking certain parts of my $HOME including
~/.emacs.d/ -- but I don't want the compiled Emacs
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sequencer.c b/sequencer.c
index dd9de49..c3a17f8 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -754,8 +754,8 @@ static void prepare_revs(struct
Will be useful for the next commits.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 102 +++-
sequencer.h | 1 +
2 files changed, 102 insertions(+), 1 deletion(-)
diff --git a/sequencer.c b/sequencer.c
index
We should free objects before leaving.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/sequencer.c b/sequencer.c
index b4989ba..f7be7d8 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -628,8
Akin to 'am --skip' and 'rebase --skip'.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
Documentation/git-cherry-pick.txt | 1 +
Documentation/git-revert.txt | 1 +
Documentation/sequencer.txt | 3 +++
builtin/revert.c | 6 ++
sequencer.c
Pretty much what it says on the tin.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
Documentation/git-cherry-pick.txt | 3 +++
builtin/revert.c| 8
sequencer.c | 6 ++
sequencer.h | 1 +
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 33 +
1 file changed, 29 insertions(+), 4 deletions(-)
diff --git a/sequencer.c b/sequencer.c
index 74480d7..6d13e63 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -14,6 +14,7 @@
#include
As we should.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 42 +-
1 file changed, 41 insertions(+), 1 deletion(-)
diff --git a/sequencer.c b/sequencer.c
index 76ff2ff..74480d7 100644
--- a/sequencer.c
+++ b/sequencer.c
@@
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
Documentation/git-cherry-pick.txt | 6 +-
Documentation/git-revert.txt | 6 +-
builtin/revert.c | 1 +
sequencer.c | 9 ++---
sequencer.h | 1 +
5 files
By using good ol' goto.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/sequencer.c b/sequencer.c
index ab6f8a7..b4989ba 100644
--- a/sequencer.c
+++ b/sequencer.c
@@ -474,7 +474,7 @@
Hi,
Sames as v2, plus a few changes from the feedback, and cleanups.
Felipe Contreras (9):
sequencer: remove useless indentation
sequencer: trivial fix
cherry-pick: add --skip-empty option
cherry-pick: store rewritten commits
sequencer: run post-rewrite hook
cherry-pick: add support
Ramkumar Ramachandra:
Yeah. We generally prefer the long-form equivalents while doing
completions, but these blame options do not have equivalent
long-forms.
Perhaps that is the real bug, then. -M and -C already have long names
for diff (and its friends), perhaps blame should have the same
On Thu, Jun 6, 2013 at 3:59 AM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 33 +
1 file changed, 29 insertions(+), 4 deletions(-)
diff --git a/sequencer.c b/sequencer.c
On 2013-06-06 03:46:59 EDT, Felipe Contreras wrote:
On Thu, Jun 6, 2013 at 2:26 AM, demerphq demer...@gmail.com wrote:
Good thing you are being objective and leaving out the Python 3.0
mess, the long legacy of backwards compatibility in the Perl
community, the active community behind it, its
Michael Haggerty mhag...@alum.mit.edu writes:
* at the source-code level, a tool in contrib can take advantage of some
of the Git build/test infrastructure, though I don't know whether they
currently do.
They do not do much AFAICT. For example, contrib/subtree/t/Makefile is
essentially
On Thu, Jun 6, 2013 at 7:24 AM, Barry Fishman barry_fish...@acm.org wrote:
On 2013-06-06 03:46:59 EDT, Felipe Contreras wrote:
On Thu, Jun 6, 2013 at 2:26 AM, demerphq demer...@gmail.com wrote:
Good thing you are being objective and leaving out the Python 3.0
mess, the long legacy of
On 2013-06-06 09:01:48 EDT, Felipe Contreras wrote:
On Thu, Jun 6, 2013 at 7:24 AM, Barry Fishman barry_fish...@acm.org wrote:
On 2013-06-06 03:46:59 EDT, Felipe Contreras wrote:
On Thu, Jun 6, 2013 at 2:26 AM, demerphq demer...@gmail.com wrote:
Good thing you are being objective and leaving
On Thu, Jun 6, 2013 at 8:46 AM, Barry Fishman barry_fish...@acm.org wrote:
On 2013-06-06 09:01:48 EDT, Felipe Contreras wrote:
Nobody is judging the usefulness of a language, I have plenty of
arguments for that, but this is about popularity.
I used usefulness in its general vague sense. It
On 6 June 2013 09:17, Stefan Haller ste...@haller-berlin.de wrote:
On Mac OS X, any application that is started from the Terminal will open
behind all running applications; as a work-around, manually bring ourselves
to the front. (Stolen from gitk, commit 76bf6ff93e.)
We do this as the very
On 2013-06-06 10:09:21 EDT, Felipe Contreras wrote:
I don't know what you are saying, but it clearly has nothing to do
with the point.
Perl is declining, and it would be wise to use another language
instead of it.
You want a simple statement. I don't particulary like Perl, but it has
worked
On Thu, Jun 6, 2013 at 9:41 AM, Barry Fishman barry_fish...@acm.org wrote:
On 2013-06-06 10:09:21 EDT, Felipe Contreras wrote:
I don't know what you are saying, but it clearly has nothing to do
with the point.
Perl is declining, and it would be wise to use another language
instead of it.
Pat Thoyts pattho...@gmail.com wrote:
On 6 June 2013 09:17, Stefan Haller ste...@haller-berlin.de wrote:
+## On Mac, bring the current Wish process window to front
+
+if {[tk windowingsystem] eq aqua} {
+ exec osascript -e [format {
+ tell application System Events
On Thu, 6 Jun 2013, Felipe Contreras wrote:
In the end my point remains unchanged; Perl is declining, so it would
be wise for the future to use another scripting language instead.
Perl use may or may not be declining (depending on how you measure it), but are
you really willing to take on
Felipe Contreras felipe.contre...@gmail.com writes:
On Thu, Jun 6, 2013 at 9:54 AM, Greg Troxel g...@ir.bbn.com wrote:
git is a core tool that people use on almost the smallest of boxes,
perhaps even replacing rcs for managing local config files. On such
machines, even perl may be large,
Jeff King p...@peff.net writes:
On Thu, Jun 06, 2013 at 01:41:05AM -0500, Felipe Contreras wrote:
Thanks. I wasn't quite clear on how the signal handling worked on
Windows, but from your description, I agree there is not any point in
running the test at all.
Shouldn't we clarify that
Jeff King p...@peff.net writes:
On Wed, Jun 05, 2013 at 12:38:23PM -0400, Jeff King wrote:
2. Actually do a reachability check. Doing a full object check to
allow fetching an arbitrary tree by sha1 is probably prohibitively
expensive[2], but we could allow the form commit[:path],
On Thu, Jun 06, 2013 at 10:21:47AM -0700, Junio C Hamano wrote:
The particular deficiency is that when a signal is raise()d whose SIG_DFL
action will cause process death (SIGTERM in this case), the
implementation of raise() just calls exit(3).
After a bit of web searching, it seems to me
Jeff King p...@peff.net writes:
Many code paths will free a tree object's buffer and set it
to NULL after finishing with it in order to keep memory
usage down during a traversal. However, out of 8 sites that
do this, only one actually unsets the parsed flag back.
Those sites that don't are
On Tue, Jun 4, 2013 at 2:53 PM, Junio C Hamano gits...@pobox.com wrote:
After reading the subject alone, my reaction was is this sorting
commits by the name of the author?
That is one of the expected natural reactions when people hear about
this option, which is not what you want.
Perhaps
Pat Thoyts pattho...@gmail.com writes:
Seems fine to me. I can't test this as I have no access to this
platform. Possibly you should run this in a catch statement so it can
ignore any errors and I would tend to use the 'auto_execok' command to
ensure that osascript actually exists. Something
On Thu, Jun 6, 2013 at 11:09 AM, David Lang da...@lang.hm wrote:
On Thu, 6 Jun 2013, Felipe Contreras wrote:
In the end my point remains unchanged; Perl is declining, so it would
be wise for the future to use another scripting language instead.
Perl use may or may not be declining
Moritz Bunkus mor...@bunkus.org writes:
This used to work until recently, though I'm not sure up to which
version excatly. I'm on Arch Linux and therefore usually pretty much
up to date. My current git version is 1.8.3.
Could you test if 'master' at 3684101a654d (Merge branch
On Thu, Jun 6, 2013 at 12:16 PM, Greg Troxel g...@ir.bbn.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
On Thu, Jun 6, 2013 at 9:54 AM, Greg Troxel g...@ir.bbn.com wrote:
git is a core tool that people use on almost the smallest of boxes,
perhaps even replacing rcs for
Felipe Contreras felipe.contre...@gmail.com writes:
Pretty much what it says on the tin.
And a bit more, isn't it?
The --keep-redundant-commits option implies the --allow-empty option
and it was perfectly acceptable to give both. By making sure that
only at most one of -k-r-d, -a-e or -s-e is
On Thu, Jun 6, 2013 at 12:21 PM, Junio C Hamano gits...@pobox.com wrote:
Jeff King p...@peff.net writes:
If somebody wants to write a note somewhere in the git
documentation, that's fine with me, but I'm not clear on exactly
what it would even say.
I agree with both points. I can suggest
On Thu, Jun 6, 2013 at 1:30 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Pretty much what it says on the tin.
And a bit more, isn't it?
The --keep-redundant-commits option implies the --allow-empty option
and it was perfectly acceptable to
Felipe Contreras felipe.contre...@gmail.com writes:
As we should.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
sequencer.c | 42 +-
1 file changed, 41 insertions(+), 1 deletion(-)
diff --git a/sequencer.c b/sequencer.c
index
On Tue, Jun 4, 2013 at 3:14 PM, Junio C Hamano gits...@pobox.com wrote:
elliottcable m...@ell.io writes:
Thus, I've added an --authorship-order version of --date-order, which relies
upon the AUTHOR_DATE instead of the COMMITTER_DATE; this means that old
commits
will continue to show up
Felipe Contreras felipe.contre...@gmail.com writes:
On Thu, Jun 6, 2013 at 1:30 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Pretty much what it says on the tin.
And a bit more, isn't it?
The --keep-redundant-commits option implies the
Felipe Contreras felipe.contre...@gmail.com writes:
On Thu, Jun 6, 2013 at 1:30 PM, Junio C Hamano gits...@pobox.com wrote:
Felipe Contreras felipe.contre...@gmail.com writes:
Pretty much what it says on the tin.
And a bit more, isn't it?
The --keep-redundant-commits option implies the
Elliott Cable m...@ell.io writes:
On Tue, Jun 4, 2013 at 3:14 PM, Junio C Hamano gits...@pobox.com wrote:
elliottcable m...@ell.io writes:
Thus, I've added an --authorship-order version of --date-order, which relies
upon the AUTHOR_DATE instead of the COMMITTER_DATE; this means that old
Wow. That's my bad entirely. I apparently hallucinated a section
suggesting that you “sign-off” commits that you'd reviewed, or
something; and I'd completely skipped the section on certifying that
you have legal rights to the work, because I'd *written* it, and
didn't think it'd be relevant.
I
Fix warnings from perlcritic's level 5 and 4. They correspond to the following
cases:
- always end a submodule with a return
- don't use the constant pragma, use the Readonly module instead
- some syntax details for maps, and others.
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Hi,
This series of commits intends to follow most of perlcritic's recommandations
in order to make the code more maintainable and readable.
I followed most recommandations from level 5 (most critical ones )to 2, but
left a great part of the level 1 ones, as they were more about personal choices
- Remove m modifier when useless (m// and // was used randomly; this makes the
code more coherent)
- Remove stringy split (split('c', ...) instead of split(/c/, ...))
- Use {}{} instead of /// when slashes or used inside the regexp so as not to
escape it.
Signed-off-by: Célestin Matte
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 44 ---
1 file changed, 26 insertions(+), 18 deletions(-)
diff --git
There is already a global variable called $url. Changing the name of the local
variable prevents future possible misunderstanding.
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
@$var structures are re-written in the following way: @{ $var }
It makes them more readable.
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 12 ++--
1 file changed, 6
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
Placing the open() call inside the do{} struct will automatically close the
filehandle if possible.
Placing the close() call outside the do{} struct is useless and will make it
fail systematically
Change the error message to state that what fails is a fork(), not a file
opening.
Use autodie to
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
This follows the following rule:
InputOutput::RequireBracedFileHandleWithPrint (Severity: 1)
The `print' and `printf' functions have a unique syntax that supports an
optional file handle argument. Conway suggests wrapping this argument in
braces to make it visually stand out from the
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 20 ++--
1 file changed, 14 insertions(+), 6 deletions(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
- strings which don't need interpolation are single-quoted for more clarity and
slight gain of performance
- interpolation is preferred over concatenation in many cases, for more clarity
- variables are always used with the ${} operator inside strings
- strings including double-quotes are written
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |1 -
1 file changed, 1 deletion(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
Empty strings are replaced by an $EMPTY constant.
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/mw-to-git/git-remote-mediawiki.perl
Elliott Cable m...@ell.io writes:
And update revs-lifo to use that same enum, without adding
use_author_date bit to rev_info.
I'll look into replacing lifo with an enum as soon as I can sit back
down to update this patch. For the moment, nothing more than
committer_date_sort and
On Wed, Jun 5, 2013 at 6:13 AM, Michael Haggerty mhag...@alum.mit.edu wrote:
But my main point is that I think it would be easier to phase out
contrib/ if there were a good alternate way of providing visibility to
satellite projects. The relevant Git wiki page [1] is the most likely
David Lang wrote:
Perl use may or may not be declining (depending on how you measure it), but
are you really willing to take on the task of re-writing everything that's
in Perl into another language and force all developers of scripts to learn
that other language? what's the ROI of this?
Отправлено с iPhonegmail--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Johannes Schindelin wrote:
My initial reaction, too. It was hard enough to get Perl included with Git
for Windows (because of that pesky Subversion dependency).
Nevertheless, we had to do it, and we did it. We will do it again, if
we get enough important code written in Ruby.
As you can see
On 06/06/2013 01:46 AM, Felipe Contreras wrote:
On Thu, Jun 6, 2013 at 2:26 AM, demerphq demer...@gmail.com wrote:
Good thing you are being objective and leaving out the Python 3.0
mess, the long legacy of backwards compatibility in the Perl
community, the active community behind it, its
Greg Troxel wrote:
It's not about what I want. It's about making choices that affect other
people, and trying to find a plan that will be overall reasonable;
that's the essence of stewardship in packaging. Compiling for just
myself is far easier.
Have you asked the SBCL or Google-Chrome
Hey,
yes, the problem is gone at 3684101a654d. Thanks.
Kind regards,
mosu
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Célestin Matte celestin.ma...@ensimag.fr writes:
Placing the open() call inside the do{} struct will automatically close the
filehandle if possible.
Placing the close() call outside the do{} struct is useless and will make it
fail systematically
Change the error message to state that what
On Fri, 7 Jun 2013, Ramkumar Ramachandra wrote:
David Lang wrote:
Perl use may or may not be declining (depending on how you measure it), but
are you really willing to take on the task of re-writing everything that's
in Perl into another language and force all developers of scripts to learn
Hello All,
If I did 'git diff HEAD^..HEAD -- file' should git not report some
kind of warning if it could not match the file? For example, if 'file'
were infact 'dir/file' and 'file' were unique, would it not be a good
idea to report that in the present working directory 'file' were not
found but
Le 06/06/2013 23:13, Junio C Hamano a écrit :
Confused. Which part of this patch moves open inside a do{} block?
This was last touched by [9/18] but it doesn't do any such thing,
either.
I must have failed the rebase, as the first part of the commit moved to
[14/18] because it modifies a part
Ramkumar Ramachandra wrote:
Git is probably the _last_ thing
to be complaining about when it comes to packaging.
It would be nice if contrib/ files supported the usual make; make
install; make clean targets. That's missing functionality that does
matter to
Le 06/06/2013 23:26, Sarma Tangirala a écrit :
Hello All,
If I did 'git diff HEAD^..HEAD -- file' should git not report some
kind of warning if it could not match the file? For example, if 'file'
were infact 'dir/file' and 'file' were unique, would it not be a good
idea to report that in
Célestin Matte celestin.ma...@ensimag.fr writes:
So using autodie may not be a good idea.
But the problem is that in the current state, open() return values are
checked, but print ones are not, although it should be.
I tried man autodie and tried to spot 'print' in the categories
list that
Célestin Matte celestin.ma...@ensimag.fr writes:
Le 06/06/2013 23:26, Sarma Tangirala a écrit :
Hello All,
If I did 'git diff HEAD^..HEAD -- file' should git not report some
kind of warning if it could not match the file? For example, if 'file'
were infact 'dir/file' and 'file' were
Le 06/06/2013 23:58, Junio C Hamano a écrit :
Célestin Matte celestin.ma...@ensimag.fr writes:
So using autodie may not be a good idea.
But the problem is that in the current state, open() return values are
checked, but print ones are not, although it should be.
I tried man autodie and
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
You can find the changes described here in the integration branches
of the repositories listed at
Junio C Hamano gits...@pobox.com writes:
If you want to do this in a multi-step series (which may not be a
bad idea), I would imagine that the enum starts as a choice between
the two: traversal-order vs committer-date-order. The first patch
would change nothing else.
And then you would add
When sorting commits topologically, the primary invariant is to emit
all children before its parent is emitted. When traversing a forked
history like this with git log C E:
ABC
\
DE
we ensure that A is emitted after all of B, C, D, and E are done, B
has to wait until
On Thu, Jun 06, 2013 at 03:41:08PM -0700, Junio C Hamano wrote:
* rr/complete-difftool (2013-06-03) 2 commits
(merged to 'next' on 2013-06-04 at 01c7611)
+ completion: clarify ls-tree, archive, show completion
+ completion: difftool takes both revs and files
Update command line
On Wed, Jun 5, 2013 at 6:40 PM, Jeff King p...@peff.net wrote:
We cannot create an archive from a blob object, so we would
not expect anyone to provide one to us. And if they do, we
will fail anyway just after the reachability check. We can
therefore optimize our reachability check to ignore
SZEDER Gábor sze...@ira.uka.de writes:
On Thu, Jun 06, 2013 at 03:41:08PM -0700, Junio C Hamano wrote:
* rr/complete-difftool (2013-06-03) 2 commits
(merged to 'next' on 2013-06-04 at 01c7611)
+ completion: clarify ls-tree, archive, show completion
+ completion: difftool takes both revs
On Thu, Jun 6, 2013 at 3:34 PM, Célestin Matte
celestin.ma...@ensimag.fr wrote:
[PATCH 08/18] Explicitely assign local variable as undef and make a proper
one-instruction-by- line indentation
s/Explicitely/Explicitly/
s/by- /by-/
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Junio C Hamano gits...@pobox.com writes:
When sorting commits topologically, the primary invariant is to emit
all children before its parent is emitted. When traversing a forked
s/its/their/;
As I needed to have an excuse to push jk/commit-info-slab topic
further (I have an unpublished
Hi,
On a relatively-empty Intel Core i7 975 @ 3.33GHz (quad-core):
Cns# cd DragonFly/
Cns# time git log sys/sys/sockbuf.h /dev/null
0.540u 0.140s 0:04.30 15.8% 0+0k 2754+55io 6484pf+0w
Cns# time git log sys/sys/sockbuf.h /dev/null
0.000u 0.030s 0:00.52 5.7% 0+0k 0+0io 0pf+0w
Cns# time
On Thu, Jun 6, 2013 at 3:34 PM, Célestin Matte
celestin.ma...@ensimag.fr wrote:
Fix warnings from perlcritic's level 5 and 4. They correspond to the following
cases:
- always end a submodule with a return
- don't use the constant pragma, use the Readonly module instead
- some syntax details
On Thu, Jun 6, 2013 at 3:34 PM, Célestin Matte
celestin.ma...@ensimag.fr wrote:
- Remove m modifier when useless (m// and // was used randomly; this makes the
code more coherent)
- Remove stringy split (split('c', ...) instead of split(/c/, ...))
- Use {}{} instead of /// when slashes or used
Eric Sunshine sunsh...@sunshineco.com writes:
- if (my ($child, $parents) = $line =~
m/^-?([a-f0-9]+) ([a-f0-9 ]+)/) {
- foreach my $parent (split(' ', $parents)) {
+ if (my ($child, $parents) = $line =~
Hi git,
I want to work on a visualization program for git. I was hoping there
was a library that would allow me to monitor a git repo for changes.
Consider it like inotify, but for a git repository (in fact, I think
it would probably have inotify under the hood).
This hypothetical library would
Hi Ram,
On Fri, 7 Jun 2013, Ramkumar Ramachandra wrote:
Johannes Schindelin wrote:
My initial reaction, too. It was hard enough to get Perl included with Git
for Windows (because of that pesky Subversion dependency).
Nevertheless, we had to do it, and we did it.
That is not quite
On Thu, Jun 6, 2013 at 3:34 PM, Célestin Matte
celestin.ma...@ensimag.fr wrote:
Signed-off-by: Célestin Matte celestin.ma...@ensimag.fr
Signed-off-by: Matthieu Moy matthieu@grenoble-inp.fr
---
contrib/mw-to-git/git-remote-mediawiki.perl | 12 ++--
1 file changed, 6
1 - 100 of 115 matches
Mail list logo
