Gargi Sharma wrote:
> 7 files changed, 15 insertions(+), 86 deletions(-)
Thanks! I like the code reduction and increased use of list.h
Were you able to finish running the test suite? I wasn't :<
> -void mru_clear(struct mru *head)
> -{
> - struct list_head *pos;
> -
Thomas Gummerer writes:
> On 01/19, Junio C Hamano wrote:
>> Thomas Gummerer writes:
>>
>> > read_cache_from() defaults to using the gitdir of the_repository. As it
>> > is mostly a convenience macro, having to pass get_git_dir() for every
>> > call
The latest maintenance release Git v2.16.1 is now available at
the usual places.
This is solely to fix a brown-paper bag bug that broke "git clone"
on case insensitive filesystems of certain projects.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The following
Jason Pyeron wrote:
>
> I am asuming that this is an issue caused by codeplex's svn
> from tfs implementation. Does anyone here have any insight?
Seems like it, even using svn(1) fails (see below)
> r27599 = 9e769d8327767a155d7b96b7cc28579cf0ed4c93 (refs/remotes/git-svn)
>
>From b18bd6babc2d6a6f79177acfa2416bb5bf2b153f Mon Sep 17 00:00:00 2001
From: Felipe Gasper
Date: Sun, 21 Jan 2018 23:01:47 -0500
Subject: [PATCH] Fix comma splices in remote.c
Signed-off-by: Felipe Gasper
---
remote.c | 12 ++--
1 file
Hi Phillip,
Thanks for pointing me to the github issue. I've added my comments to
it. For my particular issue, it was resolved by setting
"CYGWIN=noglob" as an environment variable. Hopefully it resolves
Robert's problem as well.
On Sun, Jan 21, 2018 at 3:43 PM, Philip Oakley
Signed-off-by: Ramsay Jones
---
Hi Phillip,
If you need to re-roll your 'pw/sequencer-in-process-commit' branch, could
you please squash this into the relevant patch (commit da96adcf5a,
"sequencer: run 'prepare-commit-msg' hook", 2018-01-19).
Thanks.
ATB,
Ramsay
--
I was wondering if you got my previous Email to you regarding my proposal?
best regards
Email:robertwort...@outlook.com
From: "John Cheng"
I am experiencing a strange behavior and I'm not certain if it is a
problem with golang or the cygwin version of git.
Steps to reproduce:
Use golang's os/exec library to execute
exec.Command(os.Args[1],"log","@{u}") // where os.Args[1] is either
cygwin
From: "Randall S. Becker"
Upgrade old options in config.mak.uname to currently supported
NonStop operating system versions (J06.21 and L17.xx).
Signed-off-by: Randall S. Becker
---
config.mak.uname | 29 +
1 file
From: "Randall S. Becker"
Add correct FLOSS (NonStop platform emulation) definitions into
git-compat-util.h to allow correct emulation of non-platform
behaviour. Also added NSIG definition that is not explicitly
supplied in signal.h on platform.
Signed-off-by: Randall S.
From: "Randall S. Becker"
Call setbuf(stream,NULL) to force pipe flushes not enabled by
default on the NonStop platform in wrapper.c. This may be extended
in future to a configure option.
Signed-off-by: Randall S. Becker
---
wrapper.c | 3 +++
1
From: "Randall S. Becker"
Fix missing intptr_t on NonStop in compat/regex/regcomp.c wrapped
using the __TANDEM guard define. This is done because
git-compat-util.h cannot be cleanly included into this file
without additional compile errors.
Signed-off-by: Randall S.
From: "Randall S. Becker"
Introduced TAR_EXTRACT_OPTIONS as a configuration option to change
the options of tar processing during extract. The default value is "o"
which synthesizes xof, by default.
Signed-off-by: Randall S. Becker
---
Makefile
Replace the custom calls to mru.[ch] with calls to list.h. This patch is
the final step in removing the mru API completely and inlining the logic.
This patch leads to significant code reduction and the mru API hence, is
not a useful abstraction anymore.
Signed-off-by: Gargi Sharma
On Sun, Jan 21, 2018 at 4:38 AM, René Scharfe wrote:
>
> Am 20.01.2018 um 23:24 schrieb Gargi Sharma:
> > On Sat, Jan 20, 2018 at 1:02 AM, Eric Wong wrote:
> >> Gargi Sharma wrote:
> >>> --- a/list.h
> >>> +++ b/list.h
> >>> @@ -93,6 +93,13 @@
On 01/18/2018 11:27 AM, Christoph Hellwig wrote:
[adding Chris to the Cc list - this is about the awful ext3 data=ordered
behavior of syncing the whole file system data and metadata on each
fsync]
On Wed, Jan 17, 2018 at 03:57:53PM -0800, Linus Torvalds wrote:
On Wed, Jan 17, 2018 at 3:52 PM,
--
Hello
i want to invest in your region i have some funds under my management
please let me know if we can work together on this investment plan.
Regards
Melisa Mehmet
On Sun, Jan 21, 2018 at 03:07:28AM -0500, Eric Sunshine wrote:
> On Sun, Jan 21, 2018 at 02:46:15AM -0500, Eric Sunshine wrote:
> > Yep. In pretty much any other test script, this would work (it was
> > developed in a stand-alone script), but t5601 (which nukes .git as its
> > first action) isn't
--
Hello
i want to invest in your region i have some funds under my management
please let me know if we can work together on this investment plan.
Regards
Melisa Mehmet
On Sun, Jan 21 2018, John Cheng jotted:
> Actual result:
> Suppose that cygwin git is specified, the result becomes:
> exit status 128 fatal: ambiguous argument '@u': unknown revision or
> path not in the working tree.
Given that:
$ git log @{x}
fatal: ambiguous argument '@{x}':
On Sun, Jan 21, 2018 at 6:50 AM, Duy Nguyen wrote:
> On Sun, Jan 21, 2018 at 3:33 AM, brian m. carlson
>> +test_expect_success 'clone on case-insensitive fs' '
>
> We have CASE_INSENSITIVE_FS prereq. Should we use it here? I know it
> does not harm running this test on
I am experiencing a strange behavior and I'm not certain if it is a
problem with golang or the cygwin version of git.
Steps to reproduce:
Use golang's os/exec library to execute
exec.Command(os.Args[1],"log","@{u}") // where os.Args[1] is either
cygwin git or Windows git
Expected result:
commit
On 20 January 2018 at 21:58, brian m. carlson
wrote:
> When I've made changes to the sha1_file functions, I've traditionally
> moved them away from using "sha1_file" to "object_file" to ensure that
> we make it a bit more obvious that they handle object_id structs
On 20 January 2018 at 21:44, brian m. carlson
wrote:
> On Thu, Jan 18, 2018 at 03:51:03PM +0100, Patryk Obara wrote:
>> diff --git a/sha1_file.c b/sha1_file.c
>> index 88b960316c..b7baf69041 100644
>> --- a/sha1_file.c
>> +++ b/sha1_file.c
>> @@ -1420,8 +1420,8 @@
--
Hello
i want to invest in your region i have some funds under my management
please let me know if we can work together on this investment plan.
Regards
Melisa Mehmet
On Sat, Jan 20, 2018 at 04:24:17PM +0100, lars.schnei...@autodesk.com wrote:
> +static struct encoding *git_path_check_encoding(struct attr_check_item
> *check)
> +{
> + const char *value = check->value;
> + struct encoding *enc;
> +
> + if (ATTR_TRUE(value) || ATTR_FALSE(value) ||
I am asuming that this is an issue caused by codeplex's svn from tfs
implementation. Does anyone here have any insight?
$ git --version
git version 2.15.0
$ git svn clone https://smtp4dev.svn.codeplex.com/svn smtp4dev
Initialized empty Git repository in
On Sun, 21 Jan 2018, Thomas Gummerer wrote:
> Currently 'git worktree add ' creates a new branch named after the
> basename of the path by default. If a branch with that name already
> exists, the command refuses to do anything, unless the '--force' option
> is given.
>
> However we can do a
Grattis du har vunnit € 650,000.00 i Euro Millions / Google Promo
månadsdragningar hölls den 1 januari 2018. Kontakta vår agent
Email: janosiklubos...@gmail.com
1. Fullständigt namn:
2. Adress:
3. Kön:
4. Ålder:
5. Yrke:
6. Telefon:
Robert Avtandiltayn
Online-koordinator
Currently 'git worktree add ' creates a new branch named after the
basename of the path by default. If a branch with that name already
exists, the command refuses to do anything, unless the '--force' option
is given.
However we can do a little better than that, and check the branch out if
it is
On Sat, Jan 20, 2018 at 4:09 AM, Junio C Hamano wrote:
> Nguyễn Thái Ngọc Duy writes:
>
>> The call invalidate_directory() between opendir() and warning_errno() in
>> theory could make some system calls and change errno. Prevent that by
>> warning
On Sun, Jan 21, 2018 at 3:33 AM, brian m. carlson
wrote:
> We recently introduced a regression in cloning repositories onto
> case-insensitive file systems where the repository contains multiple
> files differing only in case. In such a case, we would segfault.
Congratulation!!! Dear Email User,
We wish to notify you that your email address was automatically
generated and selected during Network Online Program GLOBAL EMAIL
RAFFLE AWARDS (G E R A) yearly International Online Promotions draw
held in New York.
You have therefore been approved to claim a
On Sun, Jan 21 2018, Ævar Arnfjörð Bjarmason jotted:
> 2007-09-10), where wasn't any reason to do this back then either, it's
s/where wasn't/where there wasn't/
> The initial motivation for this change was to make a subsequent change
> which'll also modify the refs variable smaller, since it
On Sun, Jan 21 2018, Josh Bleecher Snyder jotted:
> 3. Feature suggestion
>
> There's no direct indication of whether any given file's merge
> succeeded. Currently I sniff for merge conflicts by looking for
> "+<<< .our", which feels like an ugly kludge. Could we provide an
> explicit
On Sun, Jan 21, 2018 at 02:46:15AM -0500, Eric Sunshine wrote:
> On Sun, Jan 21, 2018 at 2:33 AM, Junio C Hamano wrote:
> > "brian m. carlson" writes:
> >> +test_expect_success 'clone on case-insensitive fs' '
> >> + o=$(git hash-object -w
37 matches
Mail list logo