> A bot could subscribe to the list and create branches in a public repo.
> (This idea feels familiar -- didn't somebody attempt this already?)
Thomas Rast maintains git notes that link git commits to their gmane
discussion, you can get them with
[remote "mailnotes"]
url = git://github.com/tras
On Fri, Nov 28, 2014 at 11:57 AM, Ramsay Jones
wrote:
> Since commit baa37bff ("mv: allow renaming to fix case on case
> insensitive filesystems", 08-05-2014), the 'git mv' command has
> been able to rename a file, to one which differs only in case,
> on a case insensitive filesystem.
>
> This res
On Wed, 2014-11-26 at 15:16 -0800, Junio C Hamano wrote:
> > $ ./src/git/contrib/workdir/git-new-workdir src/git foo master
> > mkdir: cannot create directory ‘foo’: Not a directory
> > unable to create new workdir "foo"!
>
> ;-) That comes from mkdir || fail which is indeed sufficient.
Right.
Am 23. November 2014 um 17:41 schrieb Ralf Thielow :
> From: Hartmut Henkel
>
> Signed-off-by: Hartmut Henkel
> Signed-off-by: Ralf Thielow
> ---
> Junio,
>
> please apply this patch directly to your
> tree.
I'll send a pull-request to the l10n coordinator with this change.
No need to apply di
Tcl is conventionally spelled "Tcl". The description of
option "--tcl", however, spells it "tcl". Let's follow
the convention.
Reported-by: Hartmut Henkel
Signed-off-by: Ralf Thielow
---
builtin/for-each-ref.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/for-each-
Hi,
I have a repository with a submodule and I'd like to force git to
checkout the LAST version of the submodule and not the stored one (like
git submodule update --remote), but only on some branches and without
the need to remember to add --remote every time you are on this branch.
Is there any w
Since commit baa37bff ("mv: allow renaming to fix case on case
insensitive filesystems", 08-05-2014), the 'git mv' command has
been able to rename a file, to one which differs only in case,
on a case insensitive filesystem.
This results in the 'rename (case change)' test, which used to fail
prior
[updated subject, as this is not specific to the v2.2.0 release at all]
On Fri, Nov 28, 2014 at 10:48:51AM +0100, Michael J Gruber wrote:
> Are you running gnome_keyring_deamon by any chance? It think it runs by
> default in Gnome, claims to offer gpg_agent functionality but does not
> seem to do
On Fri, Nov 28, 2014 at 04:34:09PM +0100, Michael Haggerty wrote:
> My ideal would be to invert the procedure. Let the patches in a public
> Git repository somewhere be the primary artifact, and let the review
> process be focused there. Let email be an alternative interface to the
> central review
On 11/28/2014 12:18 AM, Jeff King wrote:
On Thu, Nov 27, 2014 at 09:40:08AM -0500, Mark Levedahl wrote:
Then when you add new arguments, the hook has to search through the
parameters looking for one that matches, rather than just checking "$1"
for "amend" (and "$2" for the new option, and so on
On 14-11-28 09:31 AM, Michael Haggerty wrote:
> On 11/27/2014 06:46 PM, Torsten Bögershausen wrote:
>> On 2014-11-25 01.28, Michael Haggerty wrote:
>> []
>>> Let me list the aspects of our mailing list workflow that I find
>>> cumbersome as a contributor and reviewer:
>>>
>>> * Submitting patches t
On 11/27/2014 11:53 PM, Eric Wong wrote:
> Torsten Bögershausen wrote:
>> On 2014-11-25 01.28, Michael Haggerty wrote:
>>> [...]
>> In short:
>> We can ask every contributor, if the patch send to the mailing list
>> is available on a public Git-repo, and what the branch name is,
>> like _V2.. Does
From: "Rex Macey"
"Unable to Revert Commit ... Resolve the conflicts in your working
directory and commit them before trying the revert again". Please
help me understand how to resolve the conflicts. Here's what happened
(as best as I remember).
Created a windows folder "github_learn" (not u
On 11/27/2014 06:46 PM, Torsten Bögershausen wrote:
> On 2014-11-25 01.28, Michael Haggerty wrote:
> []
>> Let me list the aspects of our mailing list workflow that I find
>> cumbersome as a contributor and reviewer:
>>
>> * Submitting patches to the mailing list is an ordeal of configuring
>> form
Rex:
On Thu, Nov 27, 2014 at 11:35:57AM -0500, Rex Macey wrote:
> "Unable to Revert Commit ... Resolve the conflicts in your working
> directory and commit them before trying the revert again". Please
> help me understand how to resolve the conflicts. Here's what
> happened (as best as I remembe
From: "Alexander Kuleshov"
Sent: Wednesday, November 26, 2014 3:53 AM
None of these warrant the code churn, I would say.
Sorry, english is not my first language, what did you mean when
saying:
"code churn"? Code duplication or something else?
--
Hi Alexander,
The term 'churn' is originally
From: "Matthieu Moy"
Torsten Bögershausen writes:
On 2014-11-25 01.28, Michael Haggerty wrote:
[]
Let me list the aspects of our mailing list workflow that I find
cumbersome as a contributor and reviewer:
* Submitting patches to the mailing list is an ordeal of configuring
format-patch and
On Wed, Nov 19, 2014 at 1:12 AM, David Turner wrote:
>> Or will you go
>> with cityhash now.. I ask because you have another sse optimization
>> for hashmap on your watchman branch and that could reduce init time
>> for name-hash. Name-hash is used often on case-insensitive fs (less
>> often on ca
Steven Noonan schrieb am 27.11.2014 um 22:32:
>
> I'm sad to report that I'm getting test failures with this release.
> Built from git and did 'make -C t prove NO_SVN_TESTS=1' and got this
> result:
>
> $ make -j8
> $ make -C t prove NO_SVN_TESTS=1 PROVE="prove -j8"
> [...]
> Test Summary Report
19 matches
Mail list logo
