Dear
Good day
Pocket size mini foldable monopod selfie stick with bt shutter button on stick,
now only $2.7/pc ,only from us,the arcpeaks factory,2kpcs in stock now
http://arcpeaks.en.alibaba.com/product/60228194355-801021588/2015_original_factory_foldable_bluetooth_monopod_mini_selfie_stick.htm
Hi Thomas.
On 3 August 2015 at 08:52, Thomas Ferris Nicolaisen wrote:
>
> Hi,
>
> A draft of Git Rev News edition 6 is available here:
>
> https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-6.md
>
> Everyone is welcome to contribute in any section, either by editing the
> ab
On 06/14/2015 12:16 AM, brian m. carlson wrote:
> This is another series of conversions to struct object_id.
>
> This series converts more of the refs code and struct object to use
> struct object_id. It introduces an additional helper function,
> has_object_file, which is the equivalent of has_s
Hi,
A draft of Git Rev News edition 6 is available here:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-6.md
Everyone is welcome to contribute in any section, either by editing the
above page on GitHub and sending a pull request, or by commenting on
this GitHub issue:
On 07/24/2015 06:45 AM, David Turner wrote:
> This series is another chunk of the pluggable refs backend work. The
> major reason it is listed as "PATCH/RFC" is beacuse it breaks
> t9300-fast-import.sh, because fast-import wants to create a ref called
> TEMP_TAG, which would now be a pseudoref. T
On Sun, Aug 2, 2015 at 12:42 PM, Jan Viktorin wrote:
> When sending an e-mail, the client and server must
> agree on an authentication mechanism. Some servers
> (due to misconfiguration or a bug) deny valid
> credentials for certain mechanisms. In this patch,
> a new option --smtp-auth and configu
Jan Viktorin writes:
> Authen::SASL gives:
>
> No SASL mechanism found
> at /usr/share/perl5/vendor_perl/Authen/SASL.pm line 77.
> at /usr/share/perl5/core_perl/Net/SMTP.pm line 207.
>
> The SASL library does not check validity of mechanisms'
> names (or I did not find it). It just tries to loa
Michael Haggerty writes:
> Hmm, ok, so you are thinking of a remote database with high latency. I
> was thinking more of something like LMDB, with latency comparable to
> filesystem storage.
Not necessarily. The comment was more from conceptual point: "Why
share what needs not to be shared?"
>
Eric Sunshine writes:
> What I was really asking was whether this sort of checking really
> belongs in git-send-email or if it is better left to Net::SMTP (and
> Authen::SASL) to do so since they are in better positions to know what
> is valid and what is not. If the Perl module(s) generate suita
Karthik Nayak writes:
>> Even more generic would be an %(ifeq:x:y) conditional and a
>> %(currentbranch) atom:
>>
>> %(ifeq:refname:currentbranch)*%(endif)
>>
>> Those are just a couple ideas. Other variations are possible and
>> likely preferable to the specialized %(starifcurrent).
>
> This
Karthik Nayak writes:
> +test_expect_success 'no padding when `padright` length is smaller than atom
> length' '
> +cat >expect <<-\EOF &&
> +refs/heads/master|
> +refs/heads/side|
> +refs/odd/spot|
> +refs/tags/double-tag|
> +refs/tags/four|
> +refs/tags/one|
> +
Authen::SASL gives:
No SASL mechanism found
at /usr/share/perl5/vendor_perl/Authen/SASL.pm line 77.
at /usr/share/perl5/core_perl/Net/SMTP.pm line 207.
The SASL library does not check validity of mechanisms'
names (or I did not find it). It just tries to load one
that matches both the ours and
When sending an e-mail, the client and server must
agree on an authentication mechanism. Some servers
(due to misconfiguration or a bug) deny valid
credentials for certain mechanisms. In this patch,
a new option --smtp-auth and configuration entry
smtpauth are introduced. If smtp_auth is defined,
i
2015-08-02 21:42 GMT+08:00 Philip Oakley :
> Separate out the three different contribution styles for existing, new,
> and wider mis-translation contributions, with suitable headings for easy
> reference.
>
> In particular highlight the appropriate action should a Git
> mis-translation be from a di
2015-08-02 21:42 GMT+08:00 Philip Oakley :
> [Resent as first email was not picked up by vger, apologies for any
> duplicates]
>
> Hi Jiang,
>
> Recently, on the 'Git for human beings' list, a user reported a
> mistranslation and asked if/what could be done, with a suggested
> alternate text [1].
From: Lars Schneider
PROBLEM:
We run P4 servers on Linux and P4 clients on Windows. For an unknown
reason the file path for a number of files in P4 does not match the
directory path with respect to case sensitivity.
E.g. `p4 files` might return
//depot/path/to/file1
//depot/PATH/to/file2
If you
From: Lars Schneider
Hi,
I want to propose this patch as it helped us to migrate a big source code base
successfully from P4 to Git. I am sorry that I don't provide a test case, yet.
I would like to get advise on the patch and on the best strategy to provide a
test. Do you only run git-p4 integr
On Sat, Aug 1, 2015 at 2:33 PM, Eric Sunshine wrote:
> On Sat, Aug 1, 2015 at 2:48 AM, Karthik Nayak wrote:
>> On Thu, Jul 30, 2015 at 2:57 AM, Matthieu Moy
>> wrote:
>> Good point! I just was wondering if we need another atom just to print a
>> star.
>> But your points certainly are valid. I'l
From: Jacob Keller
This series incorporates the feedback from both Johan and Eric. In
addition, I included an RFC implementing suggestion from Johan regarding
per-ref merge strategies.
I split the tests for --merge/--commit/--strategy out into their own
patch to help review and keep the "one com
From: Jacob Keller
Teach documentation about the cat_sort_uniq rewriteMode that got added
at the same time as the equivalent merge strategy.
Signed-off-by: Jacob Keller
Cc: Johan Herland
Cc: Michael Haggerty
Cc: Eric Sunshine
---
Documentation/config.txt| 4 ++--
Documentation/git-notes
From: Jacob Keller
Teach git-notes about a new configuration option "notes.merge" for
selecting the default notes merge strategy. Document the option in
config.txt and git-notes.txt
Add tests for use of the configuration option. Include a test to ensure
that --strategy correctly overrides the co
From: Jacob Keller
Add new tests to ensure that --commit, --abort, and --strategy are
mutually exclusive.
Signed-off-by: Jacob Keller
---
t/t3310-notes-merge-manual-resolve.sh | 12
1 file changed, 12 insertions(+)
diff --git a/t/t3310-notes-merge-manual-resolve.sh
b/t/t3310-not
From: Jacob Keller
Teach git-notes about a new configuration option
"notes..merge" which selects the merge strategy for a
particular ref. This allows selection of merge strategy different for
each note reference, in addition to the default strategy for all
references.
Signed-off-by: Jacob Keller
On Sat, Aug 1, 2015 at 2:19 PM, Jan Viktorin wrote:
> On Sat, 1 Aug 2015 05:33:28 -0400 Eric Sunshine
> wrote:
>> On Fri, Jul 31, 2015 at 7:33 PM, Jan Viktorin
>> wrote:
>> At the very least, you will also want to update the documentation
>> (Documentation/git-send-email.txt) and, if possible,
On Sun, Aug 2, 2015 at 1:01 AM, Eric Sunshine wrote:
> Don't worry too much about it. Consider it something to keep in mind for
> future patches. I reviewed the change and it seemed okay. I mentioned it
> because one of the goals of patch submission, in addition to making an
> actual change, is to
On Sun, Aug 02, 2015 at 12:41:08AM -0700, Jacob Keller wrote:
> On Sat, Aug 1, 2015 at 7:46 PM, Eric Sunshine wrote:
> >> If conflicts arise and a strategy for automatically resolving
> >> -conflicting notes (see the -s/--strategy option) is not given,
> >> -the "manual" resolver is used. This re
On Sat, Aug 1, 2015 at 7:46 PM, Eric Sunshine wrote:
>> If conflicts arise and a strategy for automatically resolving
>> -conflicting notes (see the -s/--strategy option) is not given,
>> -the "manual" resolver is used. This resolver checks out the
>> -conflicting notes in a special worktree (`.g
27 matches
Mail list logo
