Am 12/18/2012 17:24, schrieb Jeff King:
> I am not really interested in pushing this forward myself, but I worked
> up this toy that somebody might find interesting (you can "git replace
> HEAD~20" to get dumped in an editor). It should probably handle trees,
> and it would probably make sense to d
On systems without "locale" installed, t0200-gettext-basic.sh leaked
error messages when checking if some test locales are available.
Hide them, as they are not very useful.
Signed-off-by: Junio C Hamano
---
t/lib-gettext.sh | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
ATMCard Maestro FREE LOTTO You just won £500,000. For claim send your name,
address, email & Phone No. to Email: atmcardremittanc...@qatar.io for claims.
T&Cs Apply
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordo
Add "--fail-passed-todo" option to stop the test immediately when a
test that is expected to fail succeeds. After seeing the test stop,
the developer can go to the trash directory and inspect why it failed
to fail as expected.
I usually just insert "exit" after such test with an editor, but
an op
The check_snapshot function inspects and makes sure that not cruft
outside the repository hierarchy is added to the tar archive, by
insisting that the output from "tar tf" on the resulting archive
does not contain anything that does not begin with "$prefix/".
There are two issues with this implemen
The test helper svnrdump_sim.py is used as "svnrdump" during the
execution of this test, but the arrangement had a few undesirable
things:
- it relied on symbolic links;
- unportable "export VAR=VAL" was used;
- GIT_BUILD_DIR variable was not quoted correctly;
- it assumed that the Python inte
These "expect-failure" tests were not looking for the right string
in the patch file. For example:
grep "^ *"S. E. Cipient" \$" patch5
was looking for "^ *S." in three files:
"E."
"Cipient $"
patch5
With some implementations of grep, the lack of file "E." was
reported as an
With d4a7ffa (tests: "cp -a" is a GNUism, 2012-10-08), we got rid of
most of them, but a topic that was still in flight was missed.
Signed-off-by: Junio C Hamano
---
t/t3600-rm.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/t/t3600-rm.sh b/t/t3600-rm.sh
index 97254e
Zoltan Klinger writes:
> Thanks for the feedback.
>
>> My reading of the above is that "lst" after sorting is expected to
>> have something like:
>>
>> a/
>> a/b/
>> a/b/to-be-removed
>> a/to-be-removed
>>
>> and we first show "a/", remember that prefix in "dir", n
On Wed, Dec 12, 2012 at 7:43 AM, Eric S. Raymond wrote:
> Patrick Donnelly :
>>How would another language (e.g. Python) mitigate this?
>
> The way you mitigate this sort of problem is to have a good set of
> high-level bindings for standard services (like socket I/O) built in
> your extens
Thanks for the feedback.
> My reading of the above is that "lst" after sorting is expected to
> have something like:
>
> a/
> a/b/
> a/b/to-be-removed
> a/to-be-removed
>
> and we first show "a/", remember that prefix in "dir", not show
> "a/b/" because it matches p
Thanks.
--
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
chrisc...@tuxfamily.org wrote on Tue, 18 Dec 2012 20:00 +0100:
> When make is run, the python scripts are created from *.py files that
> are changed to use the python given by PYTHON_PATH. And PYTHON_PATH
> is set by default to /usr/bin/python on Linux.
>
> This is nice except when you run make an
John Keeping writes:
> While investigating Asciidoc's quoting in this thread [1], I noticed
> that my system man pages don't display Asciidoc double quoted text
> correctly.
> ...
> I can't see any configuration option that could cause this difference,
> so I assume it must be caused by some part
On Tue, Dec 18, 2012 at 04:10:34PM -0600, Evan Driscoll wrote:
> I have two use cases of 'add -i'. The more common one is if I kind of
> want -p but don't want to do it for every file. (I guess in part this is
> my way of substituting for not knowing all the actions during -p as
> well.) But I som
On 12/18/2012 03:59 PM, Jeff King wrote:
> I always assumed nobody really used the full "add -i", but maybe it is
> because I am such a command-line snob. Evan, are you after hunk
> selection (like choosing "patch" from the interactive UI), or full path
> selection?
Mostly the latter.
I have two
From: Matt Kraai
Signed-off-by: Matt Kraai
---
Makefile | 21 +
git-compat-util.h | 6 +-
2 files changed, 26 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 2c1f04f..a39dc83 100644
--- a/Makefile
+++ b/Makefile
@@ -80,6 +80,8 @@ all::
#
From: Matt Kraai
lock is only used by fetch_pack, so move it into that function.
Signed-off-by: Matt Kraai
---
builtin/fetch-pack.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/builtin/fetch-pack.c b/builtin/fetch-pack.c
index e644398..9bc10b3 100644
--- a/builtin/fetc
This series ports Git to QNX. It differs from the previous version in
that:
* it's rebased on dm/port, so it narrows the scope of the lock
variable in builtin/fetch-pack.c instead of fetch-pack.c and uses
HAVE_STRINGS_H; and
* it disables use of Pthreads, since fork(2) doesn't work once
On Tue, Dec 18, 2012 at 01:34:38PM -0800, Junio C Hamano wrote:
> Evan Driscoll writes:
>
> > It's not infrequent that I want to discard changes I've made locally to
> > files ('git checkout file.txt') and find myself wishing that this was an
> > action available from the 'git add --interactive'
Evan Driscoll writes:
> It's not infrequent that I want to discard changes I've made locally to
> files ('git checkout file.txt') and find myself wishing that this was an
> action available from the 'git add --interactive' UI; it feels like it
> would fit in.
Hrm, not really. "git add" is about
It's not infrequent that I want to discard changes I've made locally to
files ('git checkout file.txt') and find myself wishing that this was an
action available from the 'git add --interactive' UI; it feels like it
would fit in.
Does this sound like it would be useful? I might even be able to try
Greg Troxel writes:
> *** t0070-fundamental.sh ***
> ok 1 - character classes (isspace, isalpha etc.)
> not ok - 2 mktemp to nonexistent directory prints filename
> #
> # test_must_fail test-mktemp doesnotexist/testXX 2>err &&
> # grep "doesnotexist/tes
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
The tip of the 'master' branch is a bit past 1.8.1-rc2; hopefully we
can go final around the end of the week.
Many topics are getting into good
Junio C Hamano writes:
> I seem to get a failure from
>
> git ls-files "a*"
>
> in t/t-basic.sh if I link with platform's fnmatch().
Not what you asked, but on NetBSD 5.1, libc fnmatch is used, and with
git 1.8.0.1 that test passes.
This prompted me to look at the rest of the tests. A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/12/2012 20:22, Junio C Hamano ha scritto:
> [...]
>> Note that the performance is the reason why I suggested, in a previous
>> email, that git should have some more options to format data in custom ways.
>> As an example, there is no way to tell
I seem to get a failure from
git ls-files "a*"
in t/t-basic.sh if I link with platform's fnmatch().
--
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
On 18.12.12 18:01, Junio C Hamano wrote:
> Johannes Sixt writes:
>
>>> Junio C Hamano wrote:
It could turn out that we may be able to get rid of sys/param.h
altogether, but one step at a time. Inputs from people on minority
platforms are very much appreciated---does your platform
Manlio Perillo writes:
> I'm not sure the man page is wrong and should be changed:
>
> -- usage: git diff [] [ []] [--] [...]
> ++ usage: git diff [] [ []]
Comparison of two blob objects works entirely in different way (it
is not even recursively comparing two tree-shaped things).
I do not
These tests themselves are properly protected by the GPG
prerequisite, but one of the set-up steps outside the
test_expect_success block unconditionally assumed that there is a
gpghome/ directory, which is not true if GPG is not being used.
It may be a good idea to move the whole set-up steps in t
Manlio Perillo writes:
> Il 18/12/2012 18:53, Junio C Hamano ha scritto:
>> [jch: cc'ed git-completion experts to review implementation details]
>>
>> Manlio Perillo writes:
>>
>>> The git-completion.bash script did not implemented full, git aware,
>>> support for completion, for git commands
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/12/2012 19:11, Junio C Hamano ha scritto:
> Manlio Perillo writes:
>
>> Documentation seems to suggest this is supported, but it is not true:
>>
>> $ git diff HEAD:git.c HEAD~100:git.c -- git.c
>> usage: git diff [] [ []] [--] [...]
>>
>> u
When make is run, the python scripts are created from *.py files that
are changed to use the python given by PYTHON_PATH. And PYTHON_PATH
is set by default to /usr/bin/python on Linux.
This is nice except when you run make another time setting a
different PYTHON_PATH, because, as the python script
This is clearer to many people this way.
Signed-off-by: Christian Couder
---
Makefile | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Makefile b/Makefile
index 7db8445..e055c9a 100644
--- a/Makefile
+++ b/Makefile
@@ -2183,7 +2183,7 @@ endef
GIT-SCRIPT-DEFINES: FO
It looks like we are tracking the value of TCLTK_PATH in the main
Makefile for no good reason.
This patch removes the useless code used to do this tracking.
Maybe this code should have been moved to gitk-git/Makefile by
62ba514 (Move gitk to its own subdirectory, 2007-11-17).
A patch to do that h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 18/12/2012 18:53, Junio C Hamano ha scritto:
> [jch: cc'ed git-completion experts to review implementation details]
>
> Manlio Perillo writes:
>
>> The git-completion.bash script did not implemented full, git aware,
>> support for completion, for
This is clearer to many people this way.
A similar patch has been sent to the git mailing list
for git.git.
Signed-off-by: Christian Couder
---
Hi Pat,
Here is a patch to apply to your git-gui tree following this
discussion:
http://thread.gmane.org/gmane.comp.version-control.git/211532/
Thank
From: Junio C Hamano
> Christian Couder writes:
>
>> ...
>> +GIT-TCLTK-VARS: FORCE
>> +@VARS='$(TRACK_TCLTK)'; \
>> +if test x"$$VARS" != x"`cat $@ 2>/dev/null`" ; then \
>> +echo 1>&2 "* new Tcl/Tk interpreter location"; \
>
> I think in a related patch
Manlio Perillo writes:
> Documentation seems to suggest this is supported, but it is not true:
>
> $ git diff HEAD:git.c HEAD~100:git.c -- git.c
> usage: git diff [] [ []] [--] [...]
>
> unless I'm missing something.
Neither HEAD:git.c nor HEAD~100:git.c are commits. You are
comparing two b
Hi,
sorry for the late reply.
On Fri, Dec 07, 2012 at 09:21:33AM -0800, Junio C Hamano wrote:
> Steffen Jaeckel writes:
>
> > Signed-off-by: Steffen Jaeckel
> > ---
> > contrib/completion/git-completion.bash | 9 +
> > 1 file changed, 9 insertions(+)
> >
> > diff --git a/contrib/compl
[jch: cc'ed git-completion experts to review implementation details]
Manlio Perillo writes:
> The git-completion.bash script did not implemented full, git aware,
> support for completion, for git commands that operate on files within
> the current working directory or the index.
>
> For these co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
Documentation seems to suggest this is supported, but it is not true:
$ git diff HEAD:git.c HEAD~100:git.c -- git.c
usage: git diff [] [ []] [--] [...]
unless I'm missing something.
Manlio
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
Earlier we allowed platforms that lack not to include
the header file from git-compat-util.h; we have included this header
file since the early days back when we used MAXPATHLEN (which we no
longer use) and also depended on it slurping ULONG_MAX (which we get
by including stdint.h or inttypes.h th
The git-completion.bash script did not implemented full, git aware,
support for completion, for git commands that operate on files within
the current working directory or the index.
For these commands, only long options completion was available.
As an example:
git add
will suggest all f
Christian Couder writes:
> A long time ago, gitk used to live at the root of the git.git
> repository. In 62ba514 (Move gitk to its own subdirectory,
> 2007-11-17) it was moved to a subdirectory, but some code used
> to track TCLTK_PATH was left in the main Makefile instead
> of being moved to th
Johannes Sixt writes:
>> Junio C Hamano wrote:
>>> It could turn out that we may be able to get rid of sys/param.h
>>> altogether, but one step at a time. Inputs from people on minority
>>> platforms are very much appreciated---does your platform build fine
>>> when the inclusion of the file is
Chris Rorvick writes:
> I like Johannes' suggestion of using "" in the --detach case
> instead of "" as I think it makes the reason for the
> separation more obvious at a glance.
Sounds sensible; even though the option does not require its
argument to be a branch name, the user does not have a r
On Tue, Dec 18, 2012 at 01:15:30PM +0100, Torsten Bögershausen wrote:
> I could re-produce the problem here:
> git version 1.8.0.197.g5a90748
> Mac OS X (that what I had at hands fastest)
I could reproduce it, too, on Linux.
The reason it does not always happen is that git will not re-examine th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 17/12/2012 20:42, Junio C Hamano ha scritto:
> [...]
>>> I am not sure how you would handle the last parameter to "git mv",
>>> though. That is by definition a path that does not exist,
>>> i.e. cannot be completed.
>>
>> Right, the code should be
On Mon, Dec 17, 2012 at 10:34:07PM -0800, Martin von Zweigbergk wrote:
> On Wed, Nov 23, 2011 at 10:51 AM, Junio C Hamano wrote:
> >
> > I am guilty of introducing "git reset --soft HEAD^" before I invented
> > "commit --amend" during v1.3.0 timeframe to solve the issue "soft" reset
> > originall
On Tue, Dec 18, 2012 at 02:41:57PM +0100, Yann Dirson wrote:
> > I wouldn't even want a script -- we'd end up inventing a complicated
> > command-line editor for what can simply be done by judicious use of an
> > actual text editor. How about something like the following?
>
> Well, while it does
Yann Dirson writes:
> On Mon, 17 Dec 2012 13:14:56 -0800
> Junio C Hamano wrote:
>
>> Andreas Schwab writes:
>>
>> > Christian Couder writes:
>> >
>> >> Yeah, at one point I wanted to have a command that created to craft a
>> >> new commit based on an existing one.
>> >
>> > This isn't hard t
This is clearer to many people this way.
Signed-off-by: Christian Couder
---
Makefile | 10 +-
git-gui/Makefile | 6 +++---
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/Makefile b/Makefile
index 7db8445..e055c9a 100644
--- a/Makefile
+++ b/Makefile
@@ -2183,7 +
When make is run, the python scripts are created from *.py files that
are changed to use the python given by PYTHON_PATH. And PYTHON_PATH
is set by default to /usr/bin/python on Linux.
This is nice except when you run make another time setting a
different PYTHON_PATH, because, as the python script
It looks like we are tracking the value of TCLTK_PATH in the main
Makefile for no good reason.
This patch removes the useless code used to do this tracking.
Maybe this code should have been moved to gitk-git/Makefile by
62ba514 (Move gitk to its own subdirectory, 2007-11-17).
A patch to do that h
Martin von Zweigbergk writes:
> On Wed, Nov 23, 2011 at 10:51 AM, Junio C Hamano wrote:
>>
>> I am guilty of introducing "git reset --soft HEAD^" before I invented
>> "commit --amend" during v1.3.0 timeframe to solve the issue "soft" reset
>> originally wanted to.
>
> I do use "commit --amend" a
From: Junio C Hamano
>
>> .gitignore | 1 -
>> gitk-git/.gitignore | 2 ++
>> gitk-git/Makefile | 16 ++--
>
> I'll apply the .gitignore part to my tree, but could you split the
> rest out and have Paul apply to his tree at
>
> git://ozlabs.org/~paulus/gitk.git
Ok,
A long time ago, gitk used to live at the root of the git.git
repository. In 62ba514 (Move gitk to its own subdirectory,
2007-11-17) it was moved to a subdirectory, but some code used
to track TCLTK_PATH was left in the main Makefile instead
of being moved to the new Makefile that was created in gi
Hello all,
Today Opera Software released the "Git-splitter", a small tool for
sub-modularizing code in a git repo, with complete commit history, under
the Apache 2.0 license.
It's functionality is similar to "git-subtree", but also include a command
for reversing the process.
The code i
Yann Dirson writes:
>> +EXAMPLE
>> +---
>> +
>> +Replacements (and before them, grafts) are often used to replace the
>> +parent list of a commit. Since commits are stored in a human-readable
>> +format, you can in fact change any property using the following
>> +recipe:
>> +
>> +---
On Tue, 18 Dec 2012 13:49:44 +0100
Thomas Rast wrote:
> Johannes Sixt writes:
>
> > Am 12/18/2012 12:00, schrieb Yann Dirson:
> >> On Mon, 17 Dec 2012 13:14:56 -0800
> >> Junio C Hamano wrote:
> >>
> >>> Andreas Schwab writes:
> >>>
> Christian Couder writes:
>
> > Yeah, at on
Johannes Sixt writes:
> Am 12/18/2012 12:00, schrieb Yann Dirson:
>> On Mon, 17 Dec 2012 13:14:56 -0800
>> Junio C Hamano wrote:
>>
>>> Andreas Schwab writes:
>>>
Christian Couder writes:
> Yeah, at one point I wanted to have a command that created to craft a
> new commit ba
On 18.12.12 10:55, Toralf Förster wrote:
> On 12/18/2012 02:56 AM, Andrew Ardill wrote:
>> On 18 December 2012 03:01, Toralf Förster wrote:
>>> On 12/17/2012 12:38 PM, Andrew Ardill wrote:
On 17 December 2012 21:23, Toralf Förster wrote:
> Hello,
>
> I'm faced with this situation
Am 12/18/2012 12:00, schrieb Yann Dirson:
> On Mon, 17 Dec 2012 13:14:56 -0800
> Junio C Hamano wrote:
>
>> Andreas Schwab writes:
>>
>>> Christian Couder writes:
>>>
Yeah, at one point I wanted to have a command that created to craft a
new commit based on an existing one.
>>>
>>> Thi
On Mon, 17 Dec 2012 13:14:56 -0800
Junio C Hamano wrote:
> Andreas Schwab writes:
>
> > Christian Couder writes:
> >
> >> Yeah, at one point I wanted to have a command that created to craft a
> >> new commit based on an existing one.
> >
> > This isn't hard to do, you only have to resort to pl
On 12/18/2012 02:56 AM, Andrew Ardill wrote:
> On 18 December 2012 03:01, Toralf Förster wrote:
>> On 12/17/2012 12:38 PM, Andrew Ardill wrote:
>>> On 17 December 2012 21:23, Toralf Förster wrote:
Hello,
I'm faced with this situation :
http://lists.ssl.berkeley.edu/mailman/pri
On 12/18/2012 10:55 AM, Toralf Förster wrote:
> failed test(s): t3600 t7508
>
> fixed 0
> success 8342
> failed 8
> broken 56
> total 8528
>
ick forgot these :
n22 /usr/portage/dev-vcs/git # grep -i "^not ok" /tmp/git.log | grep -v TODO
not ok - 15 Test that "git rm -f" fails if its rm fa
> Junio C Hamano wrote:
>> It could turn out that we may be able to get rid of sys/param.h
>> altogether, but one step at a time. Inputs from people on minority
>> platforms are very much appreciated---does your platform build fine
>> when the inclusion of the file is removed from git-compat-util.
"Caused the posh jewelry from excavations in nature to fight, really coming
in contact with story of Tiffany colored treasures. inch Tiffany executive
vice us president Jon King said, "This year, the 175th loved-one's birthday
of the birth of a time when
[url=http://www.tiffanyandcobracelets.co.u
Matt Kraai wrote:
Junio C Hamano wrote:
It could turn out that we may be able to get rid of sys/param.h
altogether, but one step at a time. Inputs from people on minority
platforms are very much appreciated---does your platform build fine
when the inclusion of the file is removed from git-compa
70 matches
Mail list logo
