Hi,
I've been wanting to announce Sharness [1] on this list for quite some
time now, but never managed to do so. With the release of version
0.2.4, I think it's about time to change that.
Sharness is a shell-based test harness library. It was derived from
the Git project and is basically a genera
On 07/16, Junio C Hamano wrote:
> Thomas Gummerer writes:
>
> > == Work done in the previous 12 weeks ==
> >
> > - Definition of a tentative index file v5 format [1]. This differs
> > from the proposal in making it possible to bisect the directory
> > entries and file entries, to do a binar
Thanks Junio for reading the progress report, this is just
corrected version without the errors that he pointed out.
== Work done in the previous 12 weeks ==
- Definition of a tentative index file v5 format [1]. This differs
from the proposal in making it possible to bisect the directory
entr
Hoi,
On 13-07-12 16:40, Yves Perron wrote:
> I'm wondering how to commit only selected files/folders on GIT, if even
> possible. Note, the ignore list is not a good option for me as I'd like
> to add a few files in a folder that contains many hundreds for instance.
>
> Basically, I'm looking for
Pete,
I gave the patch a try, and it seems to work great.
Only problem I realized is that it means that the git commit message
and the p4 log message end up different, because to p4 the jobs lines
are special and get stripped out, but in git it just stays part of the
commit message. So, when you
We have a tag name with some special characters. The tag name is
'Build%20V%20${bamboo.custom.jiraversion.name}%20Build%20721'. In
somecases where autocompletion is used an error is given, such as 'bash:
Build%20V%20${bamboo.custom.jiraversion.name}%20Build%20721: bad
substitution'. This can be
On Monday 16 July 2012 22:27:25 Jonathan Nieder wrote:
> Florian Achleitner wrote:
> > When it does advertise refspec like:
> > Debug: Remote helper: <- refspec
> > refs/heads/master:refs/remotes/svnfile/master it all works. Unfortunatly
> > I didn't understand that a day ago.
>
> Hm, that still d
transport-helpers can advertise the 'refspec' capability,
if not a default refspec *:* is assumed. This could be helpful
information for the reader.
Signed-off-by: Florian Achleitner
---
transport-helper.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/transport-helper.c b/tra
Make a commit on top of master.
git rebase -i origin/master
Remove the commit.
Git prints "Nothing to do" and does not rebase.
Running 'git rebase -i' when there are no local commits has 'noop' in
the first line, and with it the rebase is successful. Why is this
'noop' mandatory?
- Orgad
--
To
On Tue, 2012-07-17 at 13:46 +0300, Orgad and Raizel Shaneh wrote:
> Make a commit on top of master.
>
> git rebase -i origin/master
>
> Remove the commit.
>
> Git prints "Nothing to do" and does not rebase.
>
> Running 'git rebase -i' when there are no local commits has 'noop' in
> the first li
On Tue, Jul 17, 2012 at 11:10:39AM +0200, Jeroen Meijer wrote:
> We have a tag name with some special characters. The tag name is
> 'Build%20V%20${bamboo.custom.jiraversion.name}%20Build%20721'. In
> somecases where autocompletion is used an error is given, such as
> 'bash: Build%20V%20${bamboo.cu
Am 7/17/2012 12:55, schrieb Carlos Martín Nieto:
> But more important would be /why/ you feel that rebase -i is the tool
> you should be using. If you'd like to move the branch pointer back,
> that's what the reset command is for.
Perhaps because that's not what the OP wanted to do?
Sometimes it
Florian Achleitner wrote:
> On Monday 16 July 2012 22:27:25 Jonathan Nieder wrote:
>> Hm, that still doesn't look right. The RHS of the refspec is supposed to
>> be a _private_ namespace for the remote helper, and refs/remotes/ is
>> not private.
[...]
> remote-svn now uses get_fetch_map to retri
These patches can be added to branch mm/mediawiki-usability in pu.
For the curious: I originally had patch 2/2 in my serie, but
mistakenly discarded it during a rebase. While recovering it and
testing it, I found a typo fixed by patch 1/2.
Matthieu Moy (2):
git-remote-mediawiki: fix incorrect t
Traditionnally, pages named Foo:Bar are page 'Bar' in namespace 'Foo'.
However, it is also possible to call a page Foo:Bar if 'Foo' is not a
namespace. In this case, the actual name of the page is 'Foo:Bar', in the
main namespace. Since we can't tell with only the filename, query the
wiki for a nam
Signed-off-by: Matthieu Moy
---
contrib/mw-to-git/t/push-pull-tests.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/mw-to-git/t/push-pull-tests.sh
b/contrib/mw-to-git/t/push-pull-tests.sh
index 6692a0f..9da2dc5 100644
--- a/contrib/mw-to-git/t/push-pull-tests.sh
+
Hi,
Florian Achleitner wrote:
> --- a/transport-helper.c
> +++ b/transport-helper.c
> @@ -484,8 +484,18 @@ static int fetch_with_import(struct transport *transport,
> if (posn->status & REF_STATUS_UPTODATE)
> continue;
> if (data->refspecs)
> +
The tests for the new XDG config file code are broken because the
environoment variable `XDG_CONFIG_HOME' is never set properly,
and the tests themselves do not use `XDG_CONFIG_HOME' or `HOME'
explicitly.
The following patch series corrects this brittleness (and the
failures to which it has led):
The tests in:
t/t1306-xdg-files.sh
were failing because the git commands were using the environment
variable `XDG_CONFIG_HOME' as it was set for the user's usual
environment, rather than as set for the testing environment.
This commit provides the quickest, simplest hack to make things work;
b
Hi!
Michael G Schwern wrote:
> I've fixed the git-svn tests for SVN 1.7 and tested with SVN 1.7.5.
Thanks. git-svn is not maintained by Junio but by Eric and others on
the list. I'm cc-ing Eric and Ben Walton so they can benefit from
your work.
>
The tests in:
t/t1306-xdg-files.sh
relied on brittle conventions:
* "$HOME" and "$XDG_CONFIG_HOME" having certain values.
* The testing commands having a certain current working
directory; at least one test failed as a result.
This commit mitigates the problem by using the variables
For the sake of consistency and correctness, the acronymn `xdg'
has been capitalized (`XDG').
Signed-off-by: Michael Witten
---
t/t1306-xdg-files.sh | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/t/t1306-xdg-files.sh b/t/t1306-xdg-files.sh
index 2327047..6a3
Hi,
Michael Witten wrote:
> --- a/t/test-lib.sh
> +++ b/t/test-lib.sh
> @@ -544,6 +544,9 @@ rm -fr "$test" || {
> HOME="$TRASH_DIRECTORY"
> export HOME
>
> +XDG_CONFIG_HOME=$HOME/.config
> +export XDG_CONFIG_HOME
> +
I think this is a bad idea. The typical case is for XDG_CONFIG_HOME
not to
Michael Witten writes:
> --- a/t/test-lib.sh
> +++ b/t/test-lib.sh
> @@ -544,6 +544,9 @@ rm -fr "$test" || {
> HOME="$TRASH_DIRECTORY"
> export HOME
>
> +XDG_CONFIG_HOME=$HOME/.config
> +export XDG_CONFIG_HOME
> +
Why not just unset XDG_CONFIG_HOME?
Your match makes it look like XDG_CONFIG_
Michael Witten writes:
> The tests in:
>
> t/t1306-xdg-files.sh
>
> relied on brittle conventions:
>
> * "$HOME" and "$XDG_CONFIG_HOME" having certain values.
>
> * The testing commands having a certain current working
> directory;
Other tests (t1305-config-include.sh at least) use the
Matthieu Moy writes:
> Before your patches, the correct management of $XDG_CONFIG_HOME to
> override $HOME/.config/git/ was untested (which is unfortunate, indeed),
> but after your patch serie, the fact that the default is
> $HOME/.config/git/ is untested, which IMHO is even worse.
>
> Unsetting
On Tue, Jul 17, 2012 at 10:06 AM, Mathias Lafeldt
wrote:
> I've been wanting to announce Sharness [1] on this list for quite some
> time now, but never managed to do so. With the release of version
> 0.2.4, I think it's about time to change that.
>
> Sharness is a shell-based test harness library.
On 2012.7.17 10:44 AM, Jonathan Nieder wrote:
> Michael G Schwern wrote:
>> I've fixed the git-svn tests for SVN 1.7 and tested with SVN 1.7.5.
>
> Thanks. git-svn is not maintained by Junio but by Eric and others on
> the list. I'm cc-ing Eric and Ben Walton so they can benefit from
> your work
79a9312 (commit-tree: update the command line parsing, 2011-11-09)
updated the command line parser to understand the usual "flags first
and then non-flag arguments" order, in addition to the original and
a bit unusual "tree comes first and then zero or more -p ".
Unfortunately, ba3c69a (commit: te
On Tuesday 17 July 2012 08:48:20 Jonathan Nieder wrote:
> Florian Achleitner wrote:
> > On Monday 16 July 2012 22:27:25 Jonathan Nieder wrote:
> >> Hm, that still doesn't look right. The RHS of the refspec is supposed to
> >> be a _private_ namespace for the remote helper, and refs/remotes/ is
> >
Hi,
Florian Achleitner wrote:
> So we want the transport-helper to touch only private refs, i.e. some subdir
> of refs/, ok.
> On the other hand I thought we expect git-fetch to update the RHS of the
> passed refspec (or the default one ). How?
Now I am getting confused by terminology. By "th
First of all, thanks for you feedback, both of you. And sorry for
wasting your time . I thought that the "In-Reply-To"-header would
serve as a reference to the original patch but obviously it wasn't
enough.
On Tue, Jul 17, 2012 at 8:42 AM, Junio C Hamano wrote:
>
> I wonder if we should show the
On Tuesday 17 July 2012 16:02:12 Jonathan Nieder wrote:
> Hi,
>
> Florian Achleitner wrote:
> > So we want the transport-helper to touch only private refs, i.e. some
> > subdir of refs/, ok.
> > On the other hand I thought we expect git-fetch to update the RHS of the
> > passed refspec (or the def
On 2012.7.17 10:44 AM, Jonathan Nieder wrote:
> My advice would be to send five or so of the patches that you would
> like to be reviewed first, inline, one per message, in reply to this
> message so we can start to work on that. Presumably the patches do
> not regress git-svn's behavior but only
>From 683a230e439f1d5ac2727ce4c2a74e93804fc72b Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Wed, 11 Jul 2012 22:16:01 -0700
Subject: [PATCH 03/11] Fix Git::SVN so it can at least compile alone.
It's still very intertwined with git-svn, but that's a lot of work. This
gets things work
>From 5f0b609e9b0a70c86c46b48f0b180c96c3355a14 Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Tue, 17 Jul 2012 15:40:03 -0700
Subject: [PATCH 04/11] Extract Git::SVN::Log from git-svn.
This is a straight cut & paste. Next commit will make it work. This will
make it easier to see the
>From 8f70be0424a770c299b6a0c5bf99e4030e5e4d92 Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Thu, 12 Jul 2012 16:58:53 -0700
Subject: [PATCH 05/11] Make Git::SVN::Log work.
Changes to Git::SVN::Log to make it compile
* Change the $_git_format lexical only used by Git::SVN::Log int
>From ab67ab421dbfd248b9a198b8cc1cd9944ba6178d Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Tue, 17 Jul 2012 15:46:44 -0700
Subject: [PATCH 06/11] Move Git::SVN::Migration into its own file.
Just a straight cut & paste, the fixes come next commit.
---
git-svn.perl | 246
>From cb1a73929da15e87fa3dcc41c4cfa9ca592081fa Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Thu, 12 Jul 2012 17:14:24 -0700
Subject: [PATCH 07/11] Fix Git::SVN::Migration after its move.
Also...
* eliminate the big "import all the Git command functions" loop, nothing needs
it
any
>From 9ff49d9e91c9741d501620ac47f78d8ff8ef9983 Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Tue, 17 Jul 2012 15:51:53 -0700
Subject: [PATCH 08/11] Cut & paste Git::IndexInfo into its own file.
No other changes, those are next commit so they can be seen in the diff.
---
git-svn.perl
>From 4fd7b8574b32753dcf22ec0a592f13586b938689 Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Thu, 12 Jul 2012 17:20:02 -0700
Subject: [PATCH 09/11] Fix Git::IndexInfo so it compiles.
Only used by Git::SVN::Fetcher.
---
perl/Git/IndexInfo.pm | 2 ++
perl/Git/SVN/Fetcher.pm | 2 ++
p
>From 368d6c7883080d85f82b1eae1815834e3d59ef5e Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Tue, 17 Jul 2012 15:54:33 -0700
Subject: [PATCH 10/11] Cut & paste Git::SVN::GlobSpec into its own file.
Fixes to make it work come next commit.
---
git-svn.perl | 58
>From 5152b76800f076ba0bd528664f62d3c67966fa4e Mon Sep 17 00:00:00 2001
From: "Michael G. Schwern"
Date: Thu, 12 Jul 2012 17:25:25 -0700
Subject: [PATCH 11/11] Fix Git::SVN::GlobSpec so it works.
Only used in one place in Git::SVN, load it on demand.
That should be all the Git classes out of git
Hi,
Michael G Schwern wrote:
> There's five classes, so this is ten patches. Let me go on record again to
> state that this one-inline-patch-per-email is a lot of busy work for me.
Well, there's no need to protest and go along with it if it's a bad
idea. It's just what we've found to be the ea
Hi,
Michael G Schwern wrote:
> Ok, here goes.
>
> First patch overhauls perl/Makefile.PL to make it easier to add .pm files,
> which I'm going to be doing a lot of. Instead of having to manually add to
> the %pm hash, it scans for .pm files.
An excellent goal.
> It also moves Error.pm into a b
Hi,
Michael G Schwern wrote:
> From 683a230e439f1d5ac2727ce4c2a74e93804fc72b Mon Sep 17 00:00:00 2001
> From: "Michael G. Schwern"
> Date: Wed, 11 Jul 2012 22:16:01 -0700
Just like with patch 1, the mail body should lose the above.
> Subject: [PATCH 03/11] Fix Git::SVN so it can at least compi
Michael G Schwern wrote:
> This is a straight cut & paste. Next commit will make it work.
As mentioned in reply to patch 3, we can't take this, but by swapping
the order of the two patches it should be possible to make it work.
Jonathan
--
To unsubscribe from this list: send the line "unsubscri
m...@horowitz.name wrote on Tue, 17 Jul 2012 04:49 -0400:
> I gave the patch a try, and it seems to work great.
>
> Only problem I realized is that it means that the git commit message
> and the p4 log message end up different, because to p4 the jobs lines
> are special and get stripped out, but i
Yes, I was fixing the invalid (!pgm) condition, sorry for a non-precise
description.
Does it mean that my patch is accepted or is there something else I need to do?
--
Jakub Vrana
-Original Message-
From: Jeff King [mailto:p...@peff.net]
Sent: Monday, July 16, 2012 9:16 PM
To: Jakub
On 2012.7.17 5:01 PM, Jonathan Nieder wrote:
>> It also moves Error.pm into a bundle directory. This both makes it just
>> another directory to scan (or not scan), but it also makes it possible to
>> bundle additional modules in the future. ExtUtils::MakeMaker uses this
>> technique itself.
>
>
Thanks for the reply. Quick clarifications:
Michael G Schwern wrote:
> The man page is now man3/bundles::Error::Error.3 which is equally as incorrect
> as man3/private-Error.3. It is possible to correct that so it's man3/Error.3,
> but that's going to require some effort. Basically its in the
Junio C Hamano writes:
> * I privately received a patch that is essentially the same from
>Keshav, but I do not see it either on the list or on gmane. I
>suspect the message was sent via gmane's news submission
>interface and probably it is taking some time propagating back to
>t
"Jakub Vrana" writes:
> Yes, I was fixing the invalid (!pgm) condition, sorry for a non-precise
> description.
>
> Does it mean that my patch is accepted or is there something else I need to
> do?
The impression I got from Peff's review was that the problem
description in the proposed commit l
Ping on a seemingly stalled thread.
--
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
Jonathan Nieder writes:
> The mailing list archive at
> http://news.gmane.org/gmane.comp.version-control.git might be
> useful for seeing some examples of how it plays out in practice.
By allowing people to easily publish a completed work, and making it
easier for them to let others peek at thei
Ping on seemingly stalled discussion.
--
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
Ping on a seemingly stalled discussion (no need to rush but just
checking).
--
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
Hi,
I setup gitweb and it is working. When you click any project in gitweb
following information will be displayed
cloning git clone http://.domain.com/git/Android/Abalone.git
description email client - web hybrid
owner ciebv245a daemon
last change Thu, 10 May 2012 15:44:36 +
But in
On Fri, Apr 20, 2012 at 7:36 AM, Neil Horman wrote:
> pick_one () {
> ff=--ff
> +
> case "$1" in -n) sha1=$2; ff= ;; *) sha1=$1 ;; esac
> case "$force_rebase" in '') ;; ?*) ff= ;; esac
> output git rev-parse --verify $sha1 || die "Invalid commit name:
> $sha1"
> +
On Tue, Jul 17, 2012 at 10:08:59PM -0700, Junio C Hamano wrote:
> The impression I got from Peff's review was that the problem
> description in the proposed commit log message did not describe the
> reality at all, and the added three lines did not do what the
> message implied they do. So I do n
60 matches
Mail list logo
