On Tue, Jul 23, 2013 at 10:28 AM, Eric Sunshine 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 sort_and_merge_range_set() corner ca
On Thu, Jul 25, 2013 at 4:03 AM, Eric Sunshine wrote:
> I don't
> really consider this a good argument in favor of -Lfoo,+0 representing
> an empty range, and it's a very poor substitute for Michael Haggerty's
> more expressive proposal [1].
>
> [1]:
> http://thread.gmane.org/gmane.comp.version-c
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 empt
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 patch
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 2
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 does)
2) "git push" gives 2 errors: "fatal:
On Thu, 25 Jul 2013 15:19:48 +0300
иванов иван 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
On Thu, Jul 25, 2013 at 5:12 AM, Johannes Sixt 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 blame/log -L, how
From d0f4eca712e7cf74286bfab306763a8a571b6c95 Mon Sep 17 00:00:00 2001
From: Daniele Segato
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 user
should use one in place
On 07/24/2013 10:34 PM, Junio C Hamano wrote:
Daniele Segato 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 explained.
This is one of tho
On Thu, 25 Jul 2013 17:06:41 +0400
ксовиран 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 asteri
On 13-07-25 09:45 AM, Daniele Segato wrote:
> From d0f4eca712e7cf74286bfab306763a8a571b6c95 Mon Sep 17 00:00:00 2001
> From: Daniele Segato
> 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 w
25.07.2013, 18:28, "Konstantin Khomoutov" :
> On Thu, 25 Jul 2013 17:06:41 +0400
> ксовиран 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
On Thu, Jul 25, 2013 at 10:51 AM, ксовиран 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 filenames in a wa
On Thu, 25 Jul 2013 18:51:57 +0400
ксовиран 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 commits
[...
"Yaakov (Cygwin/X)" writes:
>>> Signed-off-by: Yaakov Selkowitz
>>
>> 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 complained nor reported breakages, so
we are good to go ;-
On Thu, 25 Jul 2013 18:51:57 +0400
ксовиран 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 commits
> >
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 the
On Wed, Jul 24, 2013 at 7:42 PM, Joern Hees 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: repository .git
On Wed, Jul 24, 2013 at 8:14 AM, Antoine Pelisse 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 only once, b
On Thu, Jul 25, 2013 at 9:12 PM, Felipe Contreras
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 Junio read them.
>
> S
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
Ondřej Bílka 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 depends on how you
On Thu, Jul 25, 2013 at 2:53 PM, Antoine Pelisse wrote:
> On Thu, Jul 25, 2013 at 9:12 PM, Felipe Contreras
> 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/"
Confirm Detail
Congratulation To The Owner Of This Email Address.
We are delighted to inform you of our Post Code Microsoft
Iberica award held in Spain. This awards is fully based on an
electronic selection, Winners were picked by computerized system, drawn
from over 43,000,00 companies and indiv
On Thu, Jul 25, 2013 at 10:40 PM, Felipe Contreras
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 would work, but I think
On Thu, Jul 25, 2013 at 01:41:13PM -0700, Junio C Hamano wrote:
> Ondřej Bílka 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 fi
Overhaul the text of the http..* 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 insertions(
Peff,
The tentative patch included in the following [REQUEST 1/1] message includes
so much of your suggested text from:
> From: Jeff King
> Date: July 23, 2013 23:42:59 PDT
> Subject: Re: [PATCH v8 4/4] config: allow http..* any user matching
>
[...]
> For (1), I wonder if the explanation would
Ondřej Bílka 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 "git checkout n
Antoine Pelisse writes:
> On Thu, Jul 25, 2013 at 10:40 PM, Felipe Contreras
> 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
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
> serv
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:
http://stackover
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
wrote:
>
> On Jul 25, 2013, at 17:40, David Aguilar wrote:
>
>> On Thu, Jul 25, 2013 at 4:19 PM, Jeremy Huddles
2013/7/26 Jiang Xin :
> 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.
>
>
On Thu, Jul 25, 2013 at 03:39:13PM -0700, Kyle J. McKay wrote:
> Overhaul the text of the http..* 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
You shoul
On Thu, Jul 25, 2013 at 06:28:50PM -0700, Junio C Hamano wrote:
> Ondřej Bílka 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 vers
Jeff King writes:
> Signed-off-by: Jeff King
>
> 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 attached, unless you s
Ralf Thielow writes:
> It's more readable if "\n" is at the end of a line.
>
> Q_("the following submodule (or one of its nested submodules)\n"
> "uses a .git directory:"
Thanks both. Perhaps we should do something like this?
-- >8 --
Subject: builtin/rm.c: consolidate error reporting for remo
Junio C Hamano writes:
> Will queue the attached, unless you spot glaring errors made by me,
> coding while drunk ;-)
... aand, it turns out that I screwed up while running "git
commit --amend" (missed "-a").
I should go to bed now.
-- >8 --
From: "Kyle J. McKay"
Date: Thu, 25 Jul 2013 15
On Jul 25, 2013, at 21:37, Jeff King wrote:
On Thu, Jul 25, 2013 at 03:39:13PM -0700, Kyle J. McKay wrote:
Overhaul the text of the http..* options documentation
providing a hopefully easier to understand itemized list of
matching behavior as suggested by and including text from
Jeff King.
---
On Jul 25, 2013, at 23:23, Kyle J. McKay wrote:
On Jul 25, 2013, at 21:37, Jeff King wrote:
You should add your S-O-B, too, for your bits.
Yes. I wanted to make certain it didn't get applied just yet. :)
Looks like it got patch snarfed anyway. ;-)
On Jul 25, 2013, at 23:07, Junio C Hamano
On Thu, Jul 25, 2013 at 07:33:16PM -0700, Gulshan Singh wrote:
> 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 ca
45 matches
Mail list logo
