Niedriges prozentuales Kreditangebot

Sehr geehrter Herr / Frau Mein Name ist Catherine Graf von CREDIT SUISSE, Bedarfskredit oder Finanzierung fr Investitionen, Projektentwicklungsfinanzierung, Geschftserweiterung, Schuldenfinanzierung Suche ist hier nicht der richtige Ort, um Geld zu bekommen. Der Zinssatz betrgt 1%. Sollten

Git Merge contributor summit notes

It was great to meet some of you in person! Some notes from the Contributor Summit at Git Merge are below. Taken in haste, so my apologies if there are any mis-statements. - Alex "Does anyone think there's a

Re: [PATCH/RFC v3 07/12] pack-objects: move in_pack out of struct object_entry

Nguyễn Thái Ngọc Duy writes: > Instead of using 8 bytes (on 64 bit arch) to store a pointer to a > pack. Use an index isntead since the number of packs should be > relatively small. > > This limits the number of packs we can handle to 16k. For now if you hit > 16k pack files

Re: [PATCH/RFC v3 04/12] pack-objects: use bitfield for object_entry::depth

Nguyễn Thái Ngọc Duy writes: > + Maximum value is 4095. > ... > + if (depth > (1 << OE_DEPTH_BITS)) > + die(_("delta chain depth %d is greater than maximum limit %d"), > + depth, (1 << OE_DEPTH_BITS)); > + Do I see an off-by-one here?

Re: Is context/directory sensitive config possible or even a god idea?

Eddy Petrișor writes: > When I saw he include.path feature ... Do you mean includeIf..path?

Re: [PATCH/RFC v3 02/12] pack-objects: turn type and in_pack_type to bitfields

Nguyễn Thái Ngọc Duy writes: > @@ -1570,7 +1576,7 @@ static void drop_reused_delta(struct object_entry > *entry) > entry->depth = 0; > > oi.sizep = >size; > - oi.typep = >type; > + oi.typep = > if (packed_object_info(entry->in_pack,

Re: [PATCH/RFC v3 01/12] pack-objects: a bit of document about struct object_entry

Nguyễn Thái Ngọc Duy writes: > The role of this comment block becomes more important after we shuffle > fields around to shrink this struct. It will be much harder to see what > field is related to what. This also documents the holes in this struct > according to pahole. > >

Is context/directory sensitive config possible or even a god idea?

Hello, In some situations one person could be involved in various multi-repository projects and need to use different user.email information, depending on the project. A simple example can be using the project specific email identity for all repositories part of Android, while using the personal

Re: git stash push -u always warns "pathspec '...' did not match any files"

Marc Strapetz writes: > Thanks, I can confirm that the misleading warning message is fixed. > > What I've noticed now is that when using -u option, Git won't warn if > the pathspec is actually not matching a file. Also, an empty stash may > be created. S..., does

Re: [PATCH v11 10/10] convert: add round trip check based on 'core.checkRoundtripEncoding'

On Fri, Mar 9, 2018 at 3:22 PM, Junio C Hamano wrote: > Eric Sunshine writes: >> On Fri, Mar 9, 2018 at 12:35 PM, wrote: >>> /* Don't encode to the default encoding */ >>> - if (!strcasecmp(value,

Re: [PATCH v11 10/10] convert: add round trip check based on 'core.checkRoundtripEncoding'

Eric Sunshine writes: > On Fri, Mar 9, 2018 at 12:35 PM, wrote: >> [...] >> Add 'core.checkRoundtripEncoding', which contains a comma separated >> list of encodings, to define for what encodings Git should check the >> conversion round trip

Re: [PATCH v11 10/10] convert: add round trip check based on 'core.checkRoundtripEncoding'

On Fri, Mar 9, 2018 at 12:35 PM, wrote: > [...] > Add 'core.checkRoundtripEncoding', which contains a comma separated > list of encodings, to define for what encodings Git should check the > conversion round trip if they are used in the 'working-tree-encoding' >

Re: [PATCH v3] fetch-pack.c: use oidset to check existence of loose object

Takuto Ikuta writes: > In repository having large number of remote refs, because to check Isn't this "When fetching from a repository with large number of refs,"? The number of refs (whether it is local or remote-tracking) the local side has has nothing to do with the

Re: [PATCH] fetch-pack.c: use oidset to check existence of loose object

Junio C Hamano writes: >> Yes. But I think the default limit for the number of loose objects, 7000, >> gives us small overhead when we do enumeration of all objects. > > Hmph, I didn't see the code that does the estimation of loose object > count before starting to enumerate,

Re: [PATCH v11 08/10] convert: advise canonical UTF encoding names

lars.schnei...@autodesk.com writes: > From: Lars Schneider > > The canonical name of an UTF encoding has the format UTF, dash, number, > and an optionally byte order in upper case (e.g. UTF-8 or UTF-16BE). > Some iconv versions support alternative names without a dash

Re: [PATCH v11 07/10] convert: check for detectable errors in UTF encodings

lars.schnei...@autodesk.com writes: > + const char *advise_msg = _( > + "The file '%s' contains a byte order " > + "mark (BOM). Please use %.6s as " > + "working-tree-encoding."); I know that

Re: [PATCH v11 06/10] convert: add 'working-tree-encoding' attribute

lars.schnei...@autodesk.com writes: > +static const char *default_encoding = "UTF-8"; > + > ... > +static const char *git_path_check_encoding(struct attr_check_item *check) > +{ > + const char *value = check->value; > + > + if (ATTR_UNSET(value) || !strlen(value)) > + return

Re: [PATCH v10 3/9] strbuf: add a case insensitive starts_with()

On Fri, Mar 09 2018, Junio C. Hamano jotted: > Lars Schneider writes: > >> I think following the boost lib makes most sense. Therefore, >> I would like to go with "istarts_with". OK with you? > > I don't care too deeply; if we took starts_with() from there, where >

Re: [PATCH v11 07/10] convert: check for detectable errors in UTF encodings

> On 09 Mar 2018, at 20:00, Junio C Hamano wrote: > > lars.schnei...@autodesk.com writes: > >> +const char *advise_msg = _( >> +"The file '%s' contains a byte order " >> +"mark (BOM). Please use %.6s

Re: [PATCH v11 07/10] convert: check for detectable errors in UTF encodings

lars.schnei...@autodesk.com writes: > + const char *advise_msg = _( > + "The file '%s' contains a byte order " > + "mark (BOM). Please use %.6s as " > + "working-tree-encoding."); I know that

Re: [PATCH] fetch-pack.c: use oidset to check existence of loose object

Takuto Ikuta writes: > Yes, I just wanted to say 'git fetch' invokes fetch-pack. > fetch-pack is skipped when running git fetch repeatedly while > remote has no update by quickfetch. So I disabled it to see the > performance of fetch-pack. In chromium repository, master

Re: [PATCH] Support long format for log-based submodule diff

Stefan Beller writes: >> $ git diff --submodule=log --submodule-log-detail=(long|short) >> >> I'm not sure what makes sense here. I welcome thoughts/discussion and >> will provide follow-up patches. > > The case of merges is usually configured with --[no-]merges, or >

[PATCH v11 04/10] utf8: add function to detect prohibited UTF-16/32 BOM

From: Lars Schneider Whenever a data stream is declared to be UTF-16BE, UTF-16LE, UTF-32BE or UTF-32LE a BOM must not be used [1]. The function returns true if this is the case. This function is used in a subsequent commit. [1]

[PATCH v11 07/10] convert: check for detectable errors in UTF encodings

From: Lars Schneider Check that new content is valid with respect to the user defined 'working-tree-encoding' attribute. Signed-off-by: Lars Schneider --- convert.c| 48 ++

[PATCH v11 09/10] convert: add tracing for 'working-tree-encoding' attribute

From: Lars Schneider Add the GIT_TRACE_WORKING_TREE_ENCODING environment variable to enable tracing for content that is reencoded with the 'working-tree-encoding' attribute. This is useful to debug encoding issues. Signed-off-by: Lars Schneider

[PATCH v11 06/10] convert: add 'working-tree-encoding' attribute

From: Lars Schneider Git recognizes files encoded with ASCII or one of its supersets (e.g. UTF-8 or ISO-8859-1) as text files. All other encodings are usually interpreted as binary and consequently built-in Git text processing tools (e.g. 'git diff') as well as most Git

[PATCH v11 03/10] strbuf: add a case insensitive starts_with()

From: Lars Schneider Check in a case insensitive manner if one string is a prefix of another string. This function is used in a subsequent commit. Signed-off-by: Lars Schneider --- git-compat-util.h | 1 + strbuf.c | 9 + 2

[PATCH v11 05/10] utf8: add function to detect a missing UTF-16/32 BOM

From: Lars Schneider If the endianness is not defined in the encoding name, then let's be strict and require a BOM to avoid any encoding confusion. The is_missing_required_utf_bom() function returns true if a required BOM is missing. The Unicode standard instructs to

[PATCH v11 01/10] strbuf: remove unnecessary NUL assignment in xstrdup_tolower()

From: Lars Schneider Since 3733e69464 (use xmallocz to avoid size arithmetic, 2016-02-22) we allocate the buffer for the lower case string with xmallocz(). This already ensures a NUL at the end of the allocated buffer. Remove the unnecessary assignment. Signed-off-by:

[PATCH v11 08/10] convert: advise canonical UTF encoding names

From: Lars Schneider The canonical name of an UTF encoding has the format UTF, dash, number, and an optionally byte order in upper case (e.g. UTF-8 or UTF-16BE). Some iconv versions support alternative names without a dash or with lower case characters. To avoid

[PATCH v11 10/10] convert: add round trip check based on 'core.checkRoundtripEncoding'

From: Lars Schneider UTF supports lossless conversion round tripping and conversions between UTF and other encodings are mostly round trip safe as Unicode aims to be a superset of all other character encodings. However, certain encodings (e.g. SHIFT-JIS) are known to

[PATCH v11 02/10] strbuf: add xstrdup_toupper()

From: Lars Schneider Create a copy of an existing string and make all characters upper case. Similar xstrdup_tolower(). This function is used in a subsequent commit. Signed-off-by: Lars Schneider --- strbuf.c | 12 strbuf.h |

[PATCH v11 00/10] convert: add support for different encodings

From: Lars Schneider Hi, Patches 1-5,9 are preparation and helper functions. Patch 6-8,10 are the actual change. Patch 8 is new. This series depends on Torsten's 8462ff43e4 (convert_to_git(): safe_crlf/checksafe becomes int conv_flags, 2018-01-13) which is already in

Good day

Good day Blessings to you,am contacting you based on a mutual benefit inheritance transaction of ($10.5 million US dollars) that has to do with your last name contact me for more details. Contact email [ gracefollyt...@gmail.com ] Regards, Mrs Grace Folly

Re: [PATCH v10 3/9] strbuf: add a case insensitive starts_with()

Lars Schneider writes: > I think following the boost lib makes most sense. Therefore, > I would like to go with "istarts_with". OK with you? I don't care too deeply; if we took starts_with() from there, where what we now want is defined as istarts_with(), then that

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

Martin Ågren writes: >> Is this ready for 'next'? > > I am not aware of any open questions or issues. You thought out loud > about how the series was structured, in particular about introducing a > successful test, then redefining it, as opposed to introducing it as a >

Re: How to use filter-branch with --state-branch?

2018-03-09 14:23 GMT+01:00 Ian Campbell : > On Fri, 2018-03-09 at 14:04 +0100, Michele Locati wrote: >> Just a couple of questions: >> >> 1. it seems to me it's not possible to process all the branches in one >> go. Am I right? > > I'm not sure, I've never done such a thing,

Re: [RFC] Rebasing merges: a jorney to the ultimate solution(RoadClear)

Hi Junio, On Thu, 8 Mar 2018, Junio C Hamano wrote: > Johannes Schindelin writes: > > >> If we are talking about a drastic change, a few more days may not be > >> sufficient, but we are not in a hurry, as this already sounds like a > >> 2.18 material anyway. > > > >

Re: [PATCH v10 7/9] convert: check for detectable errors in UTF encodings

> On 07 Mar 2018, at 19:04, Eric Sunshine wrote: > > On Wed, Mar 7, 2018 at 12:30 PM, wrote: >> Check that new content is valid with respect to the user defined >> 'working-tree-encoding' attribute. >> >> Signed-off-by: Lars Schneider

Re: [PATCH v10 3/9] strbuf: add a case insensitive starts_with()

> On 09 Mar 2018, at 00:12, Junio C Hamano wrote: > > Duy Nguyen writes: > >>> extern int starts_with(const char *str, const char *prefix); >>> +extern int startscase_with(const char *str, const char *prefix); >> >> This name is a bit hard to read. Boost

git submodule update - reset instead of checkout?

Hi everyone, I've been reading up on the current state of git submodules (our customer's customers want to use them, causing a slight groan from our customer). The usability thing I wonder about - with git submodule update, is it necessary to detach the head to the current (or upstream) head,

Re: [PATCH] fetch-pack.c: use oidset to check existence of loose object

2018-03-09 3:42 GMT+09:00 Junio C Hamano : > Takuto Ikuta writes: >> This patch stores existing loose objects in hashmap beforehand and use >> it to check existence instead of using lstat. >> >> With this patch, the number of lstat calls in `git fetch` is

Re: [PATCH] fetch-pack.c: use oidset to check existence of loose object

2018-03-09 2:19 GMT+09:00 René Scharfe : > Am 08.03.2018 um 13:06 schrieb Takuto Ikuta: >> +static int add_loose_objects_to_set(const struct object_id *oid, >> + const char *path, >> + void *data) >> +{ >> + struct

[PATCH v3] fetch-pack.c: use oidset to check existence of loose object

In repository having large number of remote refs, because to check existence of each refs in local repository, 'git fetch' ends up doing a lot of lstat(2) calls to see if it exists in loose form, which makes it slow. This patch enumerates loose objects in hashmap beforehand and uses it to check

Re: How to use filter-branch with --state-branch?

On Fri, 2018-03-09 at 14:04 +0100, Michele Locati wrote: > Just a couple of questions: > > 1. it seems to me it's not possible to process all the branches in one > go. Am I right? I'm not sure, I've never done such a thing, in fact I didn't know you could. Really all this feature does is record

[PATCH v2 1/1] fetch-pack.c: use oidset to check existence of loose object

In repository having large number of remote refs, because to check existence of each refs in local repository, 'git fetch' ends up doing a lot of lstat(2) calls to see if it exists in loose form, which makes it slow. This patch enumerates loose objects in hashmap beforehand and uses it to check

[PATCH v2 0/1] fetch-pack.c: use oidset to check existence of loose object

I removed unnecessary type cast, added comment in everthing_local(...), changed flag name and updated description. Takuto Ikuta (1): fetch-pack.c: use oidset to check existence of loose object cache.h | 2 ++ fetch-pack.c | 26 +++--- sha1_file.c | 3 +++ 3 files

Re: How to use filter-branch with --state-branch?

2018-03-08 10:40 GMT+01:00 Ian Campbell : > > On Thu, 2018-03-08 at 10:25 +0100, Ævar Arnfjörð Bjarmason wrote: > > > > The first filter-branch call required 7168 steps, so did the second > > > call... > > > I also tried without the --prune option of remote update (I had to

Re: [PATCH v1.1 1/2] t9400-git-cvsserver-server: don't rely on the output of 'test_cmp'

On Fri, Mar 9, 2018 at 12:44 AM, Junio C Hamano wrote: > SZEDER Gábor writes: >>> This makes "rm -f failures &&" unnecessary, no? >> >> Indeed, it does. > > OK, no need to resend, as I'll amend it locally before queuing > (unless there is something else

Re: What's cooking in git.git (Mar 2018, #02; Tue, 6)

On Fri, Mar 9, 2018 at 1:15 PM, Martin Ågren wrote: > On 7 March 2018 at 00:34, Junio C Hamano wrote: > >> * ma/config-page-only-in-list-mode (2018-02-21) 3 commits >> - config: change default of `pager.config` to "on" >> - config: respect

Re: recent glob expansion breakage on Windows?

On 03/08/18 23:03, Jonathan Nieder wrote: > +git-for-windows > Hi, > > Laszlo Ersek wrote: > >> Jaben reports that git-send-email is suddenly failing to expand the >> "*.patch" glob for him, at the Windows CMD prompt: >> >> - >> E:\...>git send-email --suppress-cc=author

Re: [PATCH] Support long format for log-based submodule diff

On Wed, Mar 7, 2018 at 1:11 PM, Robert Dailey wrote: > I am experimenting with a version of submodule diff (using log style) > that prints the commits brought in from merges, while excluding the > merge commits themselves. This is useful in cases where a merge commit's >