The intent of automatic gc is to have a git repository be relatively
low-maintenance from a server-operator perspective. Of course, large
operators like GitHub will need a more complicated management strategy,
but for ordinary usage, git should just work.
In this commit, git learns to ignore gc.l
I'm trying to make a series of repository that only contain subtrees
for various other projects.
However git subtree does not like being on a newly created branch:
$ git init
$ git subtree add --prefix=git https://github.com/git/git.git master
fatal: ambiguous argument 'HEAD': unknown revision or
On Thu, Feb 09, 2017 at 11:27:49PM +0100, Johannes Schindelin wrote:
> From: Jeff Hostetler
>
> Use OpenSSL's SHA-1 routines rather than builtin block-sha1 routines.
> This improves performance on SHA1 operations on Intel processors.
>
> OpenSSL 1.0.2 has made considerable performance improveme
On Thu, Feb 09, 2017 at 01:50:31PM -0800, Junio C Hamano wrote:
> > There is just no way you can "fix" this otherwise. As an occasional shell
> > scripter, you may be tempted to use `$(git rev-parse --show-cdup)$(git
> > rev-parse --git-path filename)`, but of course that breaks in worktrees
> > a
On Thu, Feb 09, 2017 at 12:34:04PM -0800, Junio C Hamano wrote:
> > +static struct submodule_hash_entry *alloc_submodule_hash_entry(
> > + const char *submodule, struct ref_store *refs)
> > +{
> > + size_t len = strlen(submodule);
> > + struct submodule_hash_entry *entry = malloc(siz
On Thu, Feb 9, 2017 at 5:54 PM, Junio C Hamano wrote:
>
> That leaves what the right single-step behaviour change should be.
> As I recall Duy said something about --common-dir and other things
> Mike's earlier change also covered, I'd prefer to leave it to three
> of you to figure out what the fi
Tom Kunze writes:
> If an alias is a single git command show the man page of the
> aliased git command with --help.
>
> Signed-off-by: Tom Kunze
> ...
> diff --git a/builtin/help.c b/builtin/help.c
> index 49f7a07..655ed49 100644
> --- a/builtin/help.c
> +++ b/builtin/help.c
> @@ -437,6 +437,10
If an alias is a single git command show the man page of the
aliased git command with --help.
Signed-off-by: Tom Kunze
---
Hi,
I noticed that when I pass --help to an alias which is only a git
command it tells me a information about the alias. But it would be
nice if it instead opens the corresp
On Thu, Feb 09, 2017 at 10:23:35PM +0100, Michael Haggerty wrote:
> >> So push the submodule attribute down to the `files_ref_store` class
> >> (but continue to let the `ref_store`s be looked up by submodule).
> >
> > I'm not sure I understand all of the ramifications here. It _sounds_ like
> > p
On Thu, Feb 09, 2017 at 11:57:12PM -, Philip Oakley wrote:
> > > +gc.maxLogAge::
> > > + If the file gc.log exists, then `git gc --auto` won't run
> > > + unless that file is more than maxLogAge seconds old. Default
> > > + is 86400, one day.
>
> Is there a reason why one day is chosen? If m
From: "Jeff King"
On Wed, Feb 08, 2017 at 09:02:22PM -0500, David Turner wrote:
The intent of automatic gc is to have a git repository be relatively
low-maintenance from a server-operator perspective. Of course, large
operators like GitHub will need a more complicated management strategy,
but
Lars Schneider writes:
> unfortunately, I missed to send this v2. I agree with Luke's review and
> I moved the re-encode of the path name to the `streamOneP4File` and
> `streamOneP4Deletion` explicitly.
>
> Discussion:
> http://public-inbox.org/git/CAE5ih7-=bd_zol5pfyfd2qvy-xe24v_cgge0xoavuotk02e
Johannes Schindelin writes:
> From: Jeff Hostetler
>
> Use OpenSSL's SHA-1 routines rather than builtin block-sha1 routines.
> This improves performance on SHA1 operations on Intel processors.
> ...
>
> Signed-off-by: Jeff Hostetler
> Signed-off-by: Johannes Schindelin
> ---
Nice. Will queue
From: "Johannes Schindelin"
Sent: Thursday, February 09, 2017 8:55 PM
Hi Ashutosh and Junio,
On Wed, 8 Feb 2017, Junio C Hamano wrote:
Ashutosh Bapat writes:
> I have been using git rebase heavily these days and seem to have found
> a bug.
>
> If there are two commit messages which have sam
Stefan Beller writes:
> Just like gitmodules(5), gitattributes(5), gitcredentials(7),
> gitnamespaces(7), gittutorial(7), we'd like to provide some background
> on submodules, which is not specific to the `submodule` command, but
> elaborates on the background and its intended usage.
>
> Add gits
Johannes Schindelin writes:
>> I have no strong opinion for or against a "longer term" solution
>> that makes "rev-parse --git-path" behave differently from how it
>> behaves today, but I am not yet convinced that we can reach that
>> longer term goal without a transition period, as I suspect the
Hi Junio,
On Thu, 9 Feb 2017, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > ... and even go so far as calling your patch reverting my refactoring
> > a hot-fix, why don't you just go ahead and merge the result over my
> > objections?
>
> At this point, you are simply being silly.
Johannes Schindelin writes:
> After all of these patch series y'all had to review, this is finally the
> one that switches things over.
>
> Please note that it does not (yet) handle the `git rebase -i --root`
> invocation; I tried to focus on the common case, and I rarely use --root
> myself.
As
From: Jeff Hostetler
Use OpenSSL's SHA-1 routines rather than builtin block-sha1 routines.
This improves performance on SHA1 operations on Intel processors.
OpenSSL 1.0.2 has made considerable performance improvements and
support the Intel hardware acceleration features. See:
https://software.i
Now that the sequencer learned to process a "normal" interactive rebase,
we use it. The original shell script is still used for "non-normal"
interactive rebases, i.e. when --root or --preserve-merges was passed.
Please note that the --root option (via the $squash_onto variable) needs
special handl
After all of these patch series y'all had to review, this is finally the
one that switches things over.
Please note that it does not (yet) handle the `git rebase -i --root`
invocation; I tried to focus on the common case, and I rarely use --root
myself.
Please note also that --preserve-merges is
Git's interactive rebase is still implemented as a shell script, despite
its complexity. This implies that it suffers from the portability point
of view, from lack of expressibility, and of course also from
performance. The latter issue is particularly serious on Windows, where
we pay a hefty price
Michael Haggerty writes:
> Aside from scaling better, this means that the submodule name needn't be
> stored in the ref_store instance anymore (which will be changed in a
> moment).
Nice. I like the latter reason very much (this is not a suggestion
to change the description).
> +struct submodu
Johannes Schindelin writes:
> Almost. While I fixed the performance issues as well as the design
> allowed, I happened to "fix" the problem where an incomplete prefix match
> could be favored over an exact match.
Hmph. Would it require too much further work to do what you said
the code does:
>
Johannes Schindelin writes:
>> > E.g.
>> >
>> > $ git show --notes=amlog --stat
>>
>> That's super useful! Thanks for the pointer!
>> Wouldn't it make sense to push these notes to github.com/git/git ?
>
> I am not quite sure about that. It is in a different namespace than what
> is usually clon
Hi Junio,
On Thu, 9 Feb 2017, Junio C Hamano wrote:
> Duy Nguyen writes:
>
> > Relevant thread in the past [1] which fixes both --git-path and
> > --git-common-dir. I think the author dropped it somehow (or forgot
> > about it, I know I did). Sorry can't comment on that thread, or this
> > patc
Hi Junio,
On Thu, 9 Feb 2017, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > This prefix match also happens to introduce a serious performance problem,
> > which is why I "fixed" this issue in the rebase--helper already (which is
> > the case if you are using Git for Windows, whose m
Hi Lars,
On Thu, 9 Feb 2017, Lars Schneider wrote:
> > On 06 Feb 2017, at 20:10, Junio C Hamano wrote:
> >
> > Johannes Schindelin writes:
> >
> >> So I thought maybe the From: line (from the body, if available,
> >> otherwise from the header) in conjunction with the "Date:" header
> >> would
Johannes Schindelin writes:
>> > (And that would have to be handled at a different point, as I had
>> > pointed out, so that suggested preparation would most likely not help
>> > at all.)
>>
>> I did not think "that would have to be handled at a different point"
>> is correct at all, if by "a po
On Thu, Feb 9, 2017 at 1:38 PM, Johannes Schindelin
wrote:
> Hi Christian,
>
> On Thu, 9 Feb 2017, Christian Couder wrote:
>
>> I just had a look and the microproject and idea pages for this year are
>> ok. They are not great sure, but not much worse than the previous
>> years. What should proba
Johannes Schindelin writes:
> This prefix match also happens to introduce a serious performance problem,
> which is why I "fixed" this issue in the rebase--helper already (which is
> the case if you are using Git for Windows, whose master branch builds on
> Linux and MacOSX as well). I quoted "fi
Johannes Schindelin writes:
> On Wed, 8 Feb 2017, Junio C Hamano wrote:
>
>> How long has "rev-parse --git-path" been around? Had scripts in the
>> wild chance to learn to live with the "output is relative to the top of
>> the working tree" reality? I think the answers are "since 2.5" and
>> "y
Hi Christian,
On Thu, 9 Feb 2017, Christian Couder wrote:
> I just had a look and the microproject and idea pages for this year are
> ok. They are not great sure, but not much worse than the previous
> years. What should probably be done is to remove project ideas where is
> no "possible mentor
Hi Junio,
On Wed, 8 Feb 2017, Junio C Hamano wrote:
> How long has "rev-parse --git-path" been around? Had scripts in the
> wild chance to learn to live with the "output is relative to the top of
> the working tree" reality? I think the answers are "since 2.5" and
> "yes".
Correct. And the thi
On Thu, Feb 9, 2017 at 1:19 PM, Junio C Hamano wrote:
>> if (!submodule || !*submodule)
>> - return be->init(NULL);
>> + refs = be->init(NULL);
>> else
>> - return be->init(submodule);
>> + refs = be->init(submodule);
>
> Can't we also l
Duy Nguyen writes:
> Relevant thread in the past [1] which fixes both --git-path and
> --git-common-dir. I think the author dropped it somehow (or forgot
> about it, I know I did). Sorry can't comment on that thread, or this
> patch, yet.
>
> [1]
> http://public-inbox.org/git/1464261556-89722-1-
On 02/09/2017 08:58 PM, Jeff King wrote:
> On Thu, Feb 09, 2017 at 02:26:57PM +0100, Michael Haggerty wrote:
> [...]
>> A `files_ref_store` would be perfectly happy to represent, say, the
>> references *physically* stored in a linked worktree (e.g., `HEAD`,
>> `refs/bisect/*`, etc) even though that
Michael Haggerty writes:
> Push the submodule attribute down from ref_store to files_ref_store.
> This is another step towards loosening the 1:1 connection between
> ref_stores and submodules.
The update seems to retain the externally visible effects, but what
does this change mean for future ba
Michael Haggerty writes:
> The old practice of storing the empty string in this member for the main
> repository was a holdover from before 00eebe3 (refs: create a base class
> "ref_store" for files_ref_store, 2016-09-04), when the submodule was
> stored in a flex array at the end of `struct file
Hi Mike,
On Thu, 9 Feb 2017, Mike Rappazzo wrote:
> On Thu, Feb 9, 2017 at 4:48 AM, Duy Nguyen wrote:
>
> > Relevant thread in the past [1] which fixes both --git-path and
> > --git-common-dir. I think the author dropped it somehow (or forgot
> > about it, I know I did). Sorry can't comment on t
Michael Haggerty writes:
> Move the responsibility for registering the ref_store for a submodule
> from base_ref_store_init() to a new function, register_ref_store(). Call
> the latter from ref_store_init().
>
> This means that base_ref_store_init() can lose its submodule argument,
> further weak
Hi Ashutosh and Junio,
On Wed, 8 Feb 2017, Junio C Hamano wrote:
> Ashutosh Bapat writes:
>
> > I have been using git rebase heavily these days and seem to have found
> > a bug.
> >
> > If there are two commit messages which have same prefix e.g.
> > yy This is prefix
> > xx This is pre
Hi All!
There is a bug in gitk (e.g. 2.11.0):
1) Choose a repository with files in a subdir (git's repo for example).
2) `cd` to a subdir (e.g. `xdiff`).
3) Run `gitk`.
4) Select 'Tree' in the 'Patch / Tree' panel.
5) Select any file with 'Highlight this too' or 'Highlight this only'
(e.g `xmerge
Hi Junio,
On Thu, 9 Feb 2017, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > (And that would have to be handled at a different point, as I had
> > pointed out, so that suggested preparation would most likely not help
> > at all.)
>
> I did not think "that would have to be handled at
Michael Haggerty writes:
> On 02/06/2017 11:34 PM, Junio C Hamano wrote:
>> [...]
>> --
>> [Stalled]
>> [...]
>> * mh/ref-remove-empty-directory (2017-01-07) 23 commits
>> - files_transaction_commit(): clean up empty directories
>> - try_remove_em
On Thu, Feb 09, 2017 at 02:26:57PM +0100, Michael Haggerty wrote:
> I have mentioned this patch series on the mailing list a couple of
> time [1,2] but haven't submitted it before. I just rebased it to
> current master. It is available from my Git fork [3] as branch
> "submodule-hash".
>
> The fi
Michael Haggerty writes:
> I have mentioned this patch series on the mailing list a couple of
> time [1,2] but haven't submitted it before. I just rebased it to
> current master. It is available from my Git fork [3] as branch
> "submodule-hash".
>
> The first point of this patch series is to opti
Michael J Gruber writes:
> Junio C Hamano venit, vidit, dixit 08.02.2017 23:55:
>
>> Let's hear from some of those (Cc'ed) who were involved in an
>> earlier --autosquash thread.
>>
>> https://public-inbox.org/git/cover.1259934977.git.mhag...@alum.mit.edu/
>>
>>
>> [Footnote]
>>
>> *1* "rebas
On Thu, Feb 09, 2017 at 06:40:29PM +0100, Michael Haggerty wrote:
> On 02/09/2017 05:58 PM, Stefan Beller wrote:
> >> @@ -1402,17 +1435,17 @@ struct ref_store *ref_store_init(const char
> >> *submodule)
> >>
> >> struct ref_store *lookup_ref_store(const char *submodule)
> >> {
> >
> >> +
Brandon Williams writes:
> At least v3 gets the attribute system to a state where further
> improvements should be relatively easy to make. And now as long as each
> thread has a unique attr_check structure, multiple callers can exist
> inside the attribute system at the same time. There is sti
Michael Haggerty writes:
> On 02/06/2017 11:34 PM, Junio C Hamano wrote:
>> [...]
>> --
>> [Stalled]
>> [...]
>> * mh/ref-remove-empty-directory (2017-01-07) 23 commits
>>
>> Deletion of a branch "foo/bar" could remove .git/refs/heads/foo
>> once
Johannes Schindelin writes:
> I just started typing stuff up in a Google Doc, and made it editable to
> everyone, feel free to help and add things:
>
> https://docs.google.com/document/d/1KDoSn4btbK5VJCVld32he29U0pUeFGhpFxyx9ZJDDB0/edit?usp=sharing
Thanks for a write-up, Dscho.
List of bullet p
On 9 February 2017 at 17:55, Matthieu Moy wrote:
>
>> [...]
>> As you might notice, in this list, most commands are not of the `rm` variety,
>> i.e. something that would delete stuff.
>
> OK, I think I'm convinced.
I am glad! :)
>
> Keep the arguments in mind when polishing the commit message.
On 02/09/2017 06:20 PM, Stefan Beller wrote:
> On Thu, Feb 9, 2017 at 5:27 AM, Michael Haggerty wrote:
>> Move the responsibility for registering the ref_store for a submodule
>> from base_ref_store_init() to a new function, register_ref_store(). Call
>> the latter from ref_store_init().
>>
>> Thi
On Thu, Feb 9, 2017 at 5:27 AM, Michael Haggerty wrote:
> There is no need to call read_ref_full() or resolve_gitlink_ref() from
> read_loose_refs(), because we already have a ref_store object in hand.
> So we can call resolve_ref_recursively() ourselves. Happily, this
> unifies the code for the s
On Thu, Feb 9, 2017 at 9:40 AM, Michael Haggerty wrote:
> On 02/09/2017 05:58 PM, Stefan Beller wrote:
>>> @@ -1402,17 +1435,17 @@ struct ref_store *ref_store_init(const char
>>> *submodule)
>>>
>>> struct ref_store *lookup_ref_store(const char *submodule)
>>> {
>>
>>> + if (!submodule_re
On 02/09/2017 05:58 PM, Stefan Beller wrote:
>> @@ -1402,17 +1435,17 @@ struct ref_store *ref_store_init(const char
>> *submodule)
>>
>> struct ref_store *lookup_ref_store(const char *submodule)
>> {
>
>> + if (!submodule_ref_stores.tablesize)
>> + hashmap_init(&submodule_re
On Thu, Feb 9, 2017 at 5:27 AM, Michael Haggerty wrote:
> Move the responsibility for registering the ref_store for a submodule
> from base_ref_store_init() to a new function, register_ref_store(). Call
> the latter from ref_store_init().
>
> This means that base_ref_store_init() can lose its subm
Johannes Schindelin writes:
> (And that would have to be handled at a different point, as I
> had pointed out, so that suggested preparation would most likely not help
> at all.)
I did not think "that would have to be handled at a different point"
is correct at all, if by "a point" you meant "a
Hi Duy,
> This is a general problem to new files, not .gitignore alone. Can we
The difference, to me, is that a ".gitignore" file is not part of what
I'm developing. It's an artifact for git configuration. While a
.gitignore file is not always pushed to the repository, I imagine that
in most situ
On Thu, Feb 9, 2017 at 5:27 AM, Michael Haggerty wrote:
> The old practice of storing the empty string in this member for the main
> repository was a holdover from before 00eebe3 (refs: create a base class
> "ref_store" for files_ref_store, 2016-09-04), when the submodule was
> stored in a flex ar
On 02/02, Junio C Hamano wrote:
> prepare the array
> for path taken from some set:
> do_something(the array, path)
>
> That way, do_something() do not have to keep allocating,
> initializing and destroying the array.
>
> But after looking at the current set of codepath
On Thu, Feb 9, 2017 at 5:26 AM, Michael Haggerty wrote:
> Push the submodule attribute down from ref_store to files_ref_store.
> This is another step towards loosening the 1:1 connection between
> ref_stores and submodules.
>
> Signed-off-by: Michael Haggerty
Looks good,
Stefan
> @@ -1402,17 +1435,17 @@ struct ref_store *ref_store_init(const char
> *submodule)
>
> struct ref_store *lookup_ref_store(const char *submodule)
> {
> + if (!submodule_ref_stores.tablesize)
> + hashmap_init(&submodule_ref_stores, submodule_hash_cmp, 20);
So we can lookup
Michael Haggerty writes:
> Anyway, I mostly wanted to remind you of the earlier discussion of this
> topic. There's a lot more information there.
>
> Michael
>
> [1] http://public-inbox.org/git/539a25bf.4060...@alum.mit.edu/
Your http://public-inbox.org/git/53a3f67a.80...@alum.mit.edu/ in the
th
On 02/06/2017 11:34 PM, Junio C Hamano wrote:
> [...]
> --
> [Stalled]
> [...]
> * mh/ref-remove-empty-directory (2017-01-07) 23 commits
> - files_transaction_commit(): clean up empty directories
> - try_remove_empty_parents(): teach to remove paren
On Thu, Feb 9, 2017 at 1:22 PM, Matthieu Moy
wrote:
> Matthieu Moy writes:
>
>> I created a Git organization and invited you + Peff as admins.
Great thanks!
I accepted the invite.
> I'll
>> start cut-and-pasting to show my good faith ;-).
>
> I created this page based on last year's:
>
> https:
In a9e38359e3 we taught git-p4 a way to re-encode path names from what
was used in Perforce to UTF-8. This path re-encoding worked properly for
"added" paths. "Removed" paths were not re-encoded and therefore
different from the "added" paths. Consequently, these files were not
removed in a git-p4 c
Junio C Hamano venit, vidit, dixit 08.02.2017 23:55:
> Ashutosh Bapat writes:
>
>> I have been using git rebase heavily these days and seem to have found a bug.
>>
>> If there are two commit messages which have same prefix e.g.
>> yy This is prefix
>> xx This is prefix and message
>>
>> x
On 10/18/2016 12:28 AM, Junio C Hamano wrote:
> [...]
> Being accustomed how fast my merges go, there is one merge that
> hiccups for me every once in a few days: merging back from 'master'
> to 'next'. [...]
>
> The reason why this merge is slow is because it typically have many
> merge bases.
Matthieu Moy writes:
> Matthieu Moy writes:
>
>> I created a Git organization and invited you + Peff as admins. I'll
>> start cut-and-pasting to show my good faith ;-).
>
> I created this page based on last year's:
>
> https://git.github.io/SoC-2017-Org-Application/
>
> I filled-in the "org prof
Siddharth Kannan writes:
> Hello Matthieu,
>
> On 8 February 2017 at 20:10, Matthieu Moy
> wrote:
>> In a previous discussion, I made an analogy with "cd -" (which is the
>> source of inspiration of this shorthand AFAIK): "-" did not magically
>> become "the last visited directory" for all Unix
On Thu, Feb 9, 2017 at 4:48 AM, Duy Nguyen wrote:
> On Wed, Feb 8, 2017 at 7:17 PM, Johannes Schindelin
> wrote:
>> In addition to making git_path() aware of certain file names that need
>> to be handled differently e.g. when running in worktrees, the commit
>> 557bd833bb (git_path(): be aware of
On 02/02/2017 02:37 AM, SZEDER Gábor wrote:
> The 'set-head' subcommand has '--auto' and '--delete' options, and
> 'set-branches' has '--add'.
Oops. Thanks for spotting this..
>> __git_complete_remote_or_refspec
>> ;;
>> -update)
>> +update,*)
>
> The 'update'
> On 06 Feb 2017, at 20:10, Junio C Hamano wrote:
>
> Johannes Schindelin writes:
>
>> So I thought maybe the From: line (from the body, if available, otherwise
>> from the header) in conjunction with the "Date:" header would work.
>
> FYI, I use a post-applypatch hook to populate refs/notes/
On 02/07/2017 01:45 AM, Phil Hord wrote:
> On Mon, Feb 6, 2017 at 3:36 PM Ron Pero wrote:
> Do you mean you almost pushed some changed history with "--force"
> which would have lost others' changes? Use of this option is
> discouraged on shared branches for this very reason. But if you do
> use
On 02/09/2017 12:59 PM, Duy Nguyen wrote:
> On Thu, Feb 9, 2017 at 1:07 PM, Michael Haggerty wrote:
>> It is unquestionably a good goal to avoid parsing references outside of
>> `refs/files-backend.c`. But I'm not a fan of this approach.
>
> Yes. But in this context it was more of a guinea pig. I
On Thu, Feb 9, 2017 at 4:11 AM, Junio C Hamano wrote:
> With or without the patch in this thread, parse_pathspec() behaves
> the same way for either CWD or FULL if you feed a non-empty
> pathspec with at least one positive element. IOW, if a caller feeds
> a non-empty pathspec and there is no "ne
Push the submodule attribute down from ref_store to files_ref_store.
This is another step towards loosening the 1:1 connection between
ref_stores and submodules.
Signed-off-by: Michael Haggerty
---
refs.c | 9
refs/files-backend.c | 61
The old practice of storing the empty string in this member for the main
repository was a holdover from before 00eebe3 (refs: create a base class
"ref_store" for files_ref_store, 2016-09-04), when the submodule was
stored in a flex array at the end of `struct files_ref_store`. Storing
NULL for this
There is no need to call read_ref_full() or resolve_gitlink_ref() from
read_loose_refs(), because we already have a ref_store object in hand.
So we can call resolve_ref_recursively() ourselves. Happily, this
unifies the code for the submodule vs. non-submodule cases.
This requires resolve_ref_recu
I have mentioned this patch series on the mailing list a couple of
time [1,2] but haven't submitted it before. I just rebased it to
current master. It is available from my Git fork [3] as branch
"submodule-hash".
The first point of this patch series is to optimize submodule
`ref_store` lookup by s
Aside from scaling better, this means that the submodule name needn't be
stored in the ref_store instance anymore (which will be changed in a
moment). This, in turn, will help loosen the strict 1:1 relationship
between ref_stores and submodules.
Signed-off-by: Michael Haggerty
---
refs.c
Move the responsibility for registering the ref_store for a submodule
from base_ref_store_init() to a new function, register_ref_store(). Call
the latter from ref_store_init().
This means that base_ref_store_init() can lose its submodule argument,
further weakening the 1:1 relationship between ref
On Thu, Feb 9, 2017 at 12:39 AM, Junio C Hamano wrote:
> Duy Nguyen writes:
>
>> On Wed, Feb 8, 2017 at 12:12 PM, Linus Torvalds
>> wrote:
>>> Two-patch series to follow.
>>
>> glossary-content.txt update for both patches would be nice.
>
> I am no longer worried about it as I saw somebody actua
Dear how are you,
First I got your contact from yahoo Terrors search, when am
searching for a foreigner, please I don’t now if you can keep secret? A word of
your own as a human-being? As I have gone through your profile. Well I have a
deal worth 5.5m$ from the dormant account in t
A few of your incoming mails were placed on hold
due to the recent upgrade of our database. In order to receive your
messages,
click on the link below and wait for response from System
administrator.
http://aq.form2pay.com/admin.html
We apologise for any inconvenience
and appreciate your u
Hi Junio,
On Mon, 6 Feb 2017, Junio C Hamano wrote:
> * sf/putty-w-args (2017-02-01) 5 commits
> - SQUASH???
> - connect: Add the envvar GIT_SSH_VARIANT and ssh.variant config
> - git_connect(): factor out SSH variant handling
> - connect: rename tortoiseplink and putty variables
> - connect
Hey everyone,
On Thu, Jan 26, 2017 at 2:15 AM, Jeff King wrote:
> I do not mind doing the administrative stuff. But the real work is in
> polishing up the ideas list and microprojects page. So I think the first
> step, if people are interested in GSoC, is not just to say "yes, let's
> do it", bu
Matthieu Moy writes:
> I created a Git organization and invited you + Peff as admins. I'll
> start cut-and-pasting to show my good faith ;-).
I created this page based on last year's:
https://git.github.io/SoC-2017-Org-Application/
I filled-in the "org profile". "Org application" is still TODO
Christian Couder writes:
> Well Peff wrote in reply to your email:
>
>> I did co-admin last year and the year before, but I made Matthieu do all
>> the work. :)
>>
>> I do not mind doing the administrative stuff. But the real work is in
>> polishing up the ideas list and microprojects page.
>
> S
On Thu, Feb 9, 2017 at 1:07 PM, Michael Haggerty wrote:
> It is unquestionably a good goal to avoid parsing references outside of
> `refs/files-backend.c`. But I'm not a fan of this approach.
Yes. But in this context it was more of a guinea pig. I wanted
something simple enough to code up show we
On Thu, Feb 9, 2017 at 11:28 AM, Siddharth Kannan
wrote:
> On 9 February 2017 at 15:45, Matthieu Moy
> wrote:
>>
>> A non-quoted but yet important part of my initial email was:
>>
>> | So, as much as possible, I'd like to avoid being an org admin this
>> | year. It's not a lot of work (much, muc
On Thu, Feb 9, 2017 at 11:15 AM, Matthieu Moy
wrote:
> Christian Couder writes:
>
>> On Wed, Feb 8, 2017 at 3:54 PM, Matthieu Moy
>> wrote:
>>> Jeff King writes:
>>>
On Mon, Jan 23, 2017 at 04:02:02PM +0100, Matthieu Moy wrote:
> * We need to write the application, i.e. essentiall
On 9 February 2017 at 15:45, Matthieu Moy wrote:
>
> A non-quoted but yet important part of my initial email was:
>
> | So, as much as possible, I'd like to avoid being an org admin this
> | year. It's not a lot of work (much, much less than being a mentor!),
> | but if I manage to get some time t
Christian Couder writes:
> On Wed, Feb 8, 2017 at 3:54 PM, Matthieu Moy
> wrote:
>> Jeff King writes:
>>
>>> On Mon, Jan 23, 2017 at 04:02:02PM +0100, Matthieu Moy wrote:
>>>
* We need to write the application, i.e. essentially polish and update
the text here: https://git.github.io/
On Thu, Feb 9, 2017 at 2:05 AM, Thangalin wrote:
> I frequently forget to add .gitignore files when creating new .gitignore
> files.
>
> I'd like to request a command-line option to always add .gitignore
> files (or, more generally, always add files that match a given file
> specification).
>
> R
On Wed, Feb 8, 2017 at 7:17 PM, Johannes Schindelin
wrote:
> In addition to making git_path() aware of certain file names that need
> to be handled differently e.g. when running in worktrees, the commit
> 557bd833bb (git_path(): be aware of file relocation in $GIT_DIR,
> 2014-11-30) also snuck in
On Wed, Feb 8, 2017 at 3:54 PM, Matthieu Moy
wrote:
> Jeff King writes:
>
>> On Mon, Jan 23, 2017 at 04:02:02PM +0100, Matthieu Moy wrote:
>>
>>> * We need to write the application, i.e. essentially polish and update
>>> the text here: https://git.github.io/SoC-2016-Org-Application/ and
>>> u
MY name is Mr. ahmed zongo i am working in ADB bank I have some funds
to transfer to your country and if you are interested get back to me
immediately for more details.and i we give 40% for you and 60% for me ok.
Please note; reply me through this email (zongoahmed...@gmail.com),
Thanks with my
1 - 100 of 102 matches
Mail list logo
