Hi Joey,
Joey Hess wrote[1]:
> Commit c334b87b30c1464a1ab563fe1fb8de5eaf0e5bac caused a reversion in
> git-cat-file --batch.
>
> With an older version:
>
> joey@gnu:~/tmp/rrr>git cat-file --batch
> :file name
> e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 blob 0
>
> With the new version:
>
> joey@wr
Junio C Hamano wrote:
> Is that accurate? My impression has been:
>
> The documentation liberally mixes US and UK English (en_US/UK)
> norms for spelling and grammar, which is somewhat unfortunate.
> In an ideal world, it would have been better if it consistently
> used only one a
When the number of open packs exceeds pack_max_fds, unuse_one_window()
is called repeatedly to attempt to release the least-recently-used
pack windows, which, as a side-effect, will also close a pack file
after closing its last open window. If a pack file has been opened,
but no windows have been
Am 01.08.2013 09:28, schrieb Jakub Narebski:
> There is also TopGit, which is feature-branch management tools (which
> seems like what you want, from what you written below).
Indeed, thank you very much for pointing me to it. I have not read the
whole documentation, but it sounds promising enough
On Thu, Aug 01, 2013 at 10:01:58PM -0400, Jonas Fonseca wrote:
> On Wed, Jul 31, 2013 at 11:11 PM, Kumar Appaiah
> wrote:
> > This commit introduces the VIEW_NO_PARENT_NAV flag and adds it to the
> > log view. This allows the scrolling commands to fall through from the
> > pager to the diff when t
On Wed, Jul 31, 2013 at 11:11 PM, Kumar Appaiah
wrote:
> This commit introduces the VIEW_NO_PARENT_NAV flag and adds it to the
> log view. This allows the scrolling commands to fall through from the
> pager to the diff when the diff is viewed in the log mode.
Thanks, works like a charm.
BTW, ple
On Thu, Aug 1, 2013 at 10:00 PM, Dale R. Worley wrote:
>> From: Duy Nguyen
>
>> > Can someone give me advice on what this code *should* do?
>>
>> It does as the function name says: given cwd, a prefix (i.e. a
>> relative path with no ".." components) and a path relative to
>> cwd+prefix, convert
Greetings from George Daniels
I am George Daniels, a Banker and credit system programmer (HSBC bank).
I saw your email address while browsing through the bank D.T.C Screen in
my office
yesterday so I decided to use this very chance to know you. I believe
we should use every opportunity to know ea
Greetings from George Daniels
I am George Daniels, a Banker and credit system programmer (HSBC bank).
I saw your email address while browsing through the bank D.T.C Screen in
my office
yesterday so I decided to use this very chance to know you. I believe
we should use every opportunity to know ea
Here is a note to explain various sections and what the readers on
this list are expected to read from them in the periodic "What's
cooking" summary. This probably should be integrated in the periodic
"A note from the maintainer" posting eventually.
The first part is mostly a boilerplate message,
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 first release candidate v1.8.4-rc1 has been tagged; only
regression fixes and l10n updates from now on.
You can find the changes described
A release candidate for Git v1.8.4-rc1 is now available for testing
at the usual places.
The release tarballs are found at:
http://code.google.com/p/git-core/downloads/list
and their SHA-1 checksums are:
ab0bb0ed36dd9c0d6425f64021a9c7d7311a2b5c git-1.8.4.rc1.tar.gz
2d3f1f07ed3bde56fac5e823
Ramsay Jones writes:
> Junio C Hamano wrote:
>> Ramsay Jones writes:
>>
I am personally in favor of this simpler solution. Comments?
>>>
>>> I had expected this to me marked for 'master'.
>>>
>>> Has this simply been overlooked, or do you have reservations about
>>> applying this patch?
Junio C Hamano wrote:
> Ramsay Jones writes:
>
>>> I am personally in favor of this simpler solution. Comments?
>>
>> I had expected this to me marked for 'master'.
>>
>> Has this simply been overlooked, or do you have reservations about
>> applying this patch?
>
> I am just being careful and
On Thu, Aug 1, 2013 at 1:02 PM, Junio C Hamano wrote:
> Brandon Casey writes:
>
>> On Thu, Aug 1, 2013 at 11:39 AM, Junio C Hamano wrote:
>>> That makes me feel somewhat uneasy. Yes, you can open/mmap/close
>>> and hold onto the contents of a file still mapped in-core, and it
>>> may not count
Greetings from George Daniels
I am George Daniels, a Banker and credit system programmer (HSBC bank).
I saw your email address while browsing through the bank D.T.C Screen in
my office
yesterday so I decided to use this very chance to know you. I believe
we should use every opportunity to know ea
Brandon Casey writes:
> On Thu, Aug 1, 2013 at 11:39 AM, Junio C Hamano wrote:
>> That makes me feel somewhat uneasy. Yes, you can open/mmap/close
>> and hold onto the contents of a file still mapped in-core, and it
>> may not count as "open filedescriptor", but do OSes allow infinite
>> such m
On Thu, Aug 1, 2013 at 12:16 PM, Brandon Casey wrote:
> On Thu, Aug 1, 2013 at 11:39 AM, Junio C Hamano wrote:
>> Brandon Casey writes:
>>
>>> I've been looking closer at uses of p->windows everywhere, and it
>>> seems that we always open_packed_git() before we try to create new
>>> windows. Th
On Thu, Aug 1, 2013 at 11:39 AM, Junio C Hamano wrote:
> Brandon Casey writes:
>
>> I've been looking closer at uses of p->windows everywhere, and it
>> seems that we always open_packed_git() before we try to create new
>> windows. There doesn't seem to be any reason that we can't continue
>> to
This will hopefully avoid questions over which spelling and grammar should
be used. Translators are of course free to create localizations for
specific English dialects.
Signed-off-by: Marc Branchaud
---
On 13-08-01 02:21 PM, Junio C Hamano wrote:
> Marc Branchaud writes:
>
>> + The documenta
Brandon Casey writes:
> I've been looking closer at uses of p->windows everywhere, and it
> seems that we always open_packed_git() before we try to create new
> windows. There doesn't seem to be any reason that we can't continue
> to use the existing open windows even after closing the pack file
Marc Branchaud writes:
> + The documentation generally follows US English (en_US) norms for spelling
> + and grammar, although most spelling variations are tolerated. Just avoid
> + mixing styles when updating existing text. If you wish to correct the
> + English of some of the existing documen
The push() method in remote-curl.c is not told and does not pass the
necessary information to underlying send-pack, so this extension
does not yet work. Leave a note in the test suite.
Signed-off-by: Junio C Hamano
---
* This is primarily to give a target for other people to shoot at;
patch
On Thu, Aug 1, 2013 at 10:12 AM, Junio C Hamano wrote:
> Brandon Casey writes:
>
>> If the refs are loose, then upload-pack will read each ref from the
>> pack (allocating one or more mmap windows) so it can peel tags and
>> advertise the underlying object. If the refs are packed and peeled,
>> t
On Thu, Aug 01, 2013 at 10:25:13AM -0700, Junio C Hamano wrote:
> > diff --git a/builtin/config.c b/builtin/config.c
> > index c35c5be..9328a90 100644
> > --- a/builtin/config.c
> > +++ b/builtin/config.c
> > @@ -589,7 +589,9 @@ int cmd_config(int argc, const char **argv, const char
> > *prefix)
Jeff King writes:
> That being said, git-config _should_ be lowercasing to match the normal
> --get code path. I think the fix (squashable on top of 6/6 + my earlier
> patch) is just:
>
> diff --git a/builtin/config.c b/builtin/config.c
> index c35c5be..9328a90 100644
> --- a/builtin/config.c
> +
Brandon Casey writes:
> If the refs are loose, then upload-pack will read each ref from the
> pack (allocating one or more mmap windows) so it can peel tags and
> advertise the underlying object. If the refs are packed and peeled,
> then upload-pack will use the peeled sha1 in the packed-refs fil
On 13-08-01 11:10 AM, Marc Branchaud wrote:
> This will hopefully avoid questions over which spelling and grammar should
> be used. Translators are of course free to create localizations for other
Oops, I should have removed the word "other" here.
M.
> specific English dialects.
This will hopefully avoid questions over which spelling and grammar should
be used. Translators are of course free to create localizations for other
specific English dialects.
Signed-off-by: Marc Branchaud
---
A little less stringent now.
Documentation/CodingGuidelines | 6 ++
Documenta
> From: Duy Nguyen
> > Can someone give me advice on what this code *should* do?
>
> It does as the function name says: given cwd, a prefix (i.e. a
> relative path with no ".." components) and a path relative to
> cwd+prefix, convert 'path' to something relative to cwd. In the
> simplest case, p
> From: Duy Nguyen
> > With the above change, the test suite runs with zero failures, so it
> > doesn't affect any common Git usage.
>
> It means the test suite is incomplete. As you can see, the commit
> introducing this change does not come with a test case to catch people
> changing this.
Wh
Jens Müller tessarakt.de> writes:
>
> Hi all!
>
> I mainly use Git for version control, but have also tried out Mercurial.
> While I don't really like Mercurial in general, the idea of maintaining
> clearly separated patches with Mercurial Queues (MQ) is quite appealing.
> Therefore, I am looki
32 matches
Mail list logo
