On Tue, Jul 23, 2013 at 10:28 AM, Eric Sunshine sunsh...@sunshineco.com wrote:
While implementing multiple -L support for git-blame, I encountered
several bugs in range-set and line-log resulting in crashes. This
series fixes those bugs.
Eric Sunshine (5):
range-set: fix
Am 7/25/2013 10:03, schrieb Eric Sunshine:
The tests in this series identify real bugs in dealing with empty
ranges, which the subsequent patches fix. The test are possible
because one can specify an empty range via blame/log -L, however, I
now realize that the ability for -L to create empty
On 22-07-13 21:35, Paul Campbell wrote:
Hi,
Sorry for the delay. Not been monitoring the list lately.
I'm afraid work stopped for two reasons. Lack of interest from the
list was the main one. I understand subtree isn't used much and
subsequently there wasn't much interest in reviewing the
I agree with the idea of maintaining git-subtree outside of contrib.
However, you would need the commitment of apenwarr, or whoever hosts
the master repo, to merge in any pull requests or we are no further
forward. (apenwarr appears not to have been active on github since
early May).
On Thu, Jul
On Thu, 25 Jul 2013 15:19:48 +0300
иванов иван xowi...@yandex.ru wrote:
hello! there is problem vith git and cyrillic (utf-8) names of
branches. branch creates perfectly, but when i clone this remote
branch to local host, there are 2 bugs:
1) git branch doesnt show checked branch with
On Thu, Jul 25, 2013 at 5:12 AM, Johannes Sixt j.s...@viscovery.net wrote:
Am 7/25/2013 10:03, schrieb Eric Sunshine:
The tests in this series identify real bugs in dealing with empty
ranges, which the subsequent patches fix. The test are possible
because one can specify an empty range via
From d0f4eca712e7cf74286bfab306763a8a571b6c95 Mon Sep 17 00:00:00 2001
From: Daniele Segato daniele.seg...@gmail.com
Date: Thu, 25 Jul 2013 15:33:18 +0200
Subject: [PATCH] git-tag man: when to use lightweight or annotated tags
stress the difference between the two with suggestion on when the
On 07/24/2013 10:34 PM, Junio C Hamano wrote:
Daniele Segato daniele.seg...@gmail.com writes:
Annotated and Lightweight tags are not the same thing
for git and you shouldn't mix them up. Annotated tags are meant for
release while lightweight tags are meant to tag random commits.
Nicely
On Thu, 25 Jul 2013 17:06:41 +0400
ксовиран xowi...@yandex.ru wrote:
hello! there is problem vith git and cyrillic (utf-8) names of
branches. branch creates perfectly, but when i clone this remote
branch to local host, there are 2 bugs:
1) git branch doesnt show checked branch with
On 13-07-25 09:45 AM, Daniele Segato wrote:
From d0f4eca712e7cf74286bfab306763a8a571b6c95 Mon Sep 17 00:00:00 2001
From: Daniele Segato daniele.seg...@gmail.com
Date: Thu, 25 Jul 2013 15:33:18 +0200
Subject: [PATCH] git-tag man: when to use lightweight or annotated tags
stress the
On Thu, Jul 25, 2013 at 10:51 AM, ксовиран xowi...@yandex.ru wrote:
problem is still here, i've got ubuntu on VM and same shared git-folder
causes this problem on Mac Os and no problems on Ubuntu.
git version on Mac is 1.8.0.1 (on Ubuntu is 1.7.10.4)
OSX filesystem code canonicalizes UTF-8
On Thu, 25 Jul 2013 18:51:57 +0400
ксовиран xowi...@yandex.ru wrote:
[...]
I'm afraid, this might be not that simple: Git received certain
tweaks to work around certain problems Mac OS X has (as I
understand it) with handling UTF-8 on various filesystems it
supports; in particular, see
Yaakov (Cygwin/X) yselkow...@users.sourceforge.net writes:
Signed-off-by: Yaakov Selkowitz yselkow...@users.sourceforge.net
Will queue and wait for somebody from Cygwin land to comment.
Ping? Is there someone in particular whose input you are looking for?
Nobody in particular. Nobody
On Thu, 25 Jul 2013 18:51:57 +0400
ксовиран xowi...@yandex.ru wrote:
[...]
I'm afraid, this might be not that simple: Git received certain
tweaks to work around certain problems Mac OS X has (as I
understand it) with handling UTF-8 on various filesystems it
supports; in particular, see
Hi,
When I do git grep then with big codebase (gcc) it executes slowly.
I am thinking to add option to speed up search time.
One solution would be to use same trick as was done in google code.
Build and keep database of trigraphs and which files contain how many of
them. When querry is made
On Wed, Jul 24, 2013 at 7:42 PM, Joern Hees d...@joernhees.de wrote:
6796d49 introduced a bug by making shared_path == .git/hg' which
will most likely exist already, causing a new remote never to be
cloned and subsequently causing hg.share to fail with error msg:
mercurial.error.RepoError:
On Wed, Jul 24, 2013 at 8:14 AM, Antoine Pelisse apeli...@gmail.com wrote:
IOW, the goal is to have only one copy of each hg object that are
shared amongst many remotes (and potentially import them only once,
though I don't think it currently works for me).
That's right. I had code to import
On Thu, Jul 25, 2013 at 9:12 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Besides, I don't see
the point of having a '.shared/.hg' directory, and nothing else on
that '.shared' folder.
Is it not already true about the .git/hg/$alias/clone/ directory ?
So, here's my patch. If only
We mention twice that the from_ident field of struct
pretty_print_context is internal.
The first comment was added by 10f2fbf, which prepares the
struct for internal fields, and then the second by a908047,
which actually adds such a field. This was a mistake made
when re-rolling the series on the
On Thu, Jul 25, 2013 at 08:29:05PM +0200, Ondřej Bílka wrote:
One solution would be to use same trick as was done in google code.
Build and keep database of trigraphs and which files contain how many of
them. When querry is made then check
only these files that have appropriate combination of
Ondřej Bílka nel...@seznam.cz writes:
One solution would be to use same trick as was done in google code.
Build and keep database of trigraphs and which files contain how many of
them. When querry is made then check
only these files that have appropriate combination of trigraphs.
This
On Thu, Jul 25, 2013 at 2:53 PM, Antoine Pelisse apeli...@gmail.com wrote:
On Thu, Jul 25, 2013 at 9:12 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Besides, I don't see
the point of having a '.shared/.hg' directory, and nothing else on
that '.shared' folder.
Is it not already
On Thu, Jul 25, 2013 at 10:40 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
That's true. Maybe something like:
for x in repos:
local_hg = os.path.join(shared_path, x, 'clone', '.hg')
if os.path.exists(local_hg):
shutil.copytree(local_hg, hg_path)
break
I think that
On Thu, Jul 25, 2013 at 01:41:13PM -0700, Junio C Hamano wrote:
Ondřej Bílka nel...@seznam.cz writes:
One solution would be to use same trick as was done in google code.
Build and keep database of trigraphs and which files contain how many of
them. When querry is made then check
only
Overhaul the text of the http.url.* options documentation
providing a hopefully easier to understand itemized list of
matching behavior as suggested by and including text from
Jeff King.
---
Documentation/config.txt | 60 +---
1 file changed, 37
Peff,
The tentative patch included in the following [REQUEST 1/1] message includes
so much of your suggested text from:
From: Jeff King p...@peff.net
Date: July 23, 2013 23:42:59 PDT
Subject: Re: [PATCH v8 4/4] config: allow http.url.* any user matching
[...]
For (1), I wonder if the
Ondřej Bílka nel...@seznam.cz writes:
If grepping random commit in history is important use case then keeping
db information in history makes sense. Otherwise just having database
for current version and updating it on the fly as version changes is
enough.
Will you reindex every time I do
Antoine Pelisse apeli...@gmail.com writes:
On Thu, Jul 25, 2013 at 10:40 PM, Felipe Contreras
felipe.contre...@gmail.com wrote:
That's true. Maybe something like:
for x in repos:
local_hg = os.path.join(shared_path, x, 'clone', '.hg')
if os.path.exists(local_hg):
On 2013-07-25 14.19, иванов иван wrote:
hello! there is problem vith git and cyrillic (utf-8) names of branches.
branch creates perfectly, but when i clone this remote branch to local host,
there are 2 bugs:
1) git branch doesnt show checked branch with asterisk (while on remote
server it
I've been trying to figure out why I can't push from a shallow clone
(using --depth) to a repository. I've made simple examples where it
works, but I've read that in doesn't work in every case. However, I
can't come up with a case where it doesn't work. Googling gives this
answer:
Hi,
Commit v1.8.3-1-g914dc02 (rm: better error message on failure for
multiple files)
introduced many messages need to be translated. I found two similar messages
each has a slight typo, and the differences cause redundant works for
l10n translators.
# builtin/rm.c, line: 90
[cc:ed Eric Sunshine and the Git list since folks might be
interested.. not quite [PATCH] ready yet, but it's not too far...]
On Thu, Jul 25, 2013 at 6:00 PM, Jeremy Huddleston Sequoia
jerem...@apple.com wrote:
On Jul 25, 2013, at 17:40, David Aguilar dav...@gmail.com wrote:
On Thu, Jul 25,
2013/7/26 Jiang Xin worldhello@gmail.com:
Hi,
Commit v1.8.3-1-g914dc02 (rm: better error message on failure for
multiple files)
introduced many messages need to be translated. I found two similar messages
each has a slight typo, and the differences cause redundant works for
l10n
On Thu, Jul 25, 2013 at 03:39:13PM -0700, Kyle J. McKay wrote:
Overhaul the text of the http.url.* options documentation
providing a hopefully easier to understand itemized list of
matching behavior as suggested by and including text from
Jeff King.
---
Signed-off-by: Jeff King
On Thu, Jul 25, 2013 at 06:28:50PM -0700, Junio C Hamano wrote:
Ondřej Bílka nel...@seznam.cz writes:
If grepping random commit in history is important use case then keeping
db information in history makes sense. Otherwise just having database
for current version and updating it on the
Jeff King p...@peff.net writes:
Signed-off-by: Jeff King p...@peff.net
You should add your S-O-B, too, for your bits.
...
So this patch looks pretty good to me; the two points I raised above are
how I would have done it, but they are relatively minor if you do not
agree.
Will queue the
36 matches
Mail list logo
