Jens Lehmann jens.lehm...@web.de writes:
Am 02.06.2013 20:50, schrieb Junio C Hamano:
Jens Lehmann jens.lehm...@web.de writes:
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jl/submodule-mv (2013-04-23) 5 commits
(merged to 'next' on 2013-04-23 at c04f574)
+ submodule.c: duplicate
On Tue, Jun 04, 2013 at 06:57:34PM -0400, Phil Hord wrote:
On Tue, Jun 4, 2013 at 8:48 AM, John Keeping j...@keeping.me.uk wrote:
The problem is that sometimes you do want to adjust the path and
sometimes you don't. Reading git-submodule(1), it says:
This may be either an absolute
On Tue, Jun 04, 2013 at 09:10:45AM +0100, John Keeping wrote:
On Tue, Jun 04, 2013 at 03:29:51PM +1000, Heiko Voigt wrote:
On Mon, Jun 03, 2013 at 11:23:41PM +0100, John Keeping wrote:
Sorry, I should have been more specific here. I saw that you did some
changes to make submodule add do
On Tue, Jun 04, 2013 at 09:17:17PM +1000, Heiko Voigt wrote:
On Tue, Jun 04, 2013 at 09:10:45AM +0100, John Keeping wrote:
On Tue, Jun 04, 2013 at 03:29:51PM +1000, Heiko Voigt wrote:
On Mon, Jun 03, 2013 at 11:23:41PM +0100, John Keeping wrote:
Sorry, I should have been more specific
On Tue, Jun 04, 2013 at 11:39:25PM +0200, Jens Lehmann wrote:
Am 04.06.2013 14:48, schrieb John Keeping:
The problem is that sometimes you do want to adjust the path and
sometimes you don't. Reading git-submodule(1), it says:
This may be either an absolute URL, or (if it begins
On Tue, Jun 4, 2013 at 8:48 AM, John Keeping j...@keeping.me.uk wrote:
On Tue, Jun 04, 2013 at 09:17:17PM +1000, Heiko Voigt wrote:
On Tue, Jun 04, 2013 at 09:10:45AM +0100, John Keeping wrote:
On Tue, Jun 04, 2013 at 03:29:51PM +1000, Heiko Voigt wrote:
On Mon, Jun 03, 2013 at 11:23:41PM
John Keeping j...@keeping.me.uk writes:
I started looking at this over the weekend but didn't get time to get
something ready to be submitted. I did find a couple of issues in
cmd_foreach that make me think this topic should be dropped when next
is rewound and held in pu waiting for a
Am 02.06.2013 20:50, schrieb Junio C Hamano:
Jens Lehmann jens.lehm...@web.de writes:
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jl/submodule-mv (2013-04-23) 5 commits
(merged to 'next' on 2013-04-23 at c04f574)
+ submodule.c: duplicate real_path's return value
(merged to 'next'
Am 31.05.2013 21:40, schrieb John Keeping:
On Thu, May 30, 2013 at 09:23:40PM +0200, Jens Lehmann wrote:
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jk/submodule-subdirectory-ok (2013-04-24) 3 commits
(merged to 'next' on 2013-04-24 at 6306b29)
+ submodule: fix quoting in
On Mon, Jun 03, 2013 at 11:47:23PM +0200, Jens Lehmann wrote:
Am 31.05.2013 21:40, schrieb John Keeping:
The current version does make '$sm_path' relative in submodule
foreach, although it's hard to spot because we have to leave doing so
until right before the eval.
Yes. If I read the
On Mon, Jun 03, 2013 at 11:23:41PM +0100, John Keeping wrote:
Sorry, I should have been more specific here. I saw that you did some
changes to make submodule add do the right thing with relative paths,
but the following change to t7406 does not work like I believe it
should but instead
Jens Lehmann jens.lehm...@web.de writes:
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jl/submodule-mv (2013-04-23) 5 commits
(merged to 'next' on 2013-04-23 at c04f574)
+ submodule.c: duplicate real_path's return value
(merged to 'next' on 2013-04-19 at 45ae3c9)
+ rm: delete
Thomas Rast tr...@inf.ethz.ch writes:
This interacts with the tests from
* fc/at-head (2013-05-08) 13 commits
to fail valgrind in t1508 like so:
==22927== Invalid read of size 1
==22927==at 0x4C2C71B: __GI_strnlen (mc_replace_strmem.c:377)
==22927==by 0x567FF6B: vfprintf
Junio C Hamano gitster at pobox.com writes:
* kb/status-ignored-optim-2 (2013-05-29) 1 commit
- dir.c: fix ignore processing within not-ignored directories
Fix 1.8.3 regressions in the .gitignore path exclusion logic.
Hi,
I see that the Tested-by line in kb/status-ignored-optim-2
On Thu, May 30, 2013 at 09:23:40PM +0200, Jens Lehmann wrote:
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jk/submodule-subdirectory-ok (2013-04-24) 3 commits
(merged to 'next' on 2013-04-24 at 6306b29)
+ submodule: fix quoting in relative_path()
(merged to 'next' on 2013-04-22 at
Junio C Hamano gits...@pobox.com writes:
* rr/die-on-missing-upstream (2013-05-22) 2 commits
- sha1_name: fix error message for @{N}, @{date}
- sha1_name: fix error message for @{u}
When a reflog notation is used for implicit current branch, we
did not say which branch and worse said
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jl/submodule-mv (2013-04-23) 5 commits
(merged to 'next' on 2013-04-23 at c04f574)
+ submodule.c: duplicate real_path's return value
(merged to 'next' on 2013-04-19 at 45ae3c9)
+ rm: delete .gitmodules entry of submodules removed from the
Am 30.05.2013 01:58, schrieb Junio C Hamano:
* jk/submodule-subdirectory-ok (2013-04-24) 3 commits
(merged to 'next' on 2013-04-24 at 6306b29)
+ submodule: fix quoting in relative_path()
(merged to 'next' on 2013-04-22 at f211e25)
+ submodule: drop the top-level requirement
+
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'.
Usually I avoid issuing What's cooking back-to-back, but because I
will be offline for a few days, here is a snapshot of tonight's
status.
19 matches
Mail list logo