Today I learned that software can be constipated.
On Thu, Sep 18, 2014 at 12:35 PM, Junio C Hamano wrote:
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majord
On Mon, Feb 18, 2013 at 1:52 PM, Jay Townsend wrote:
> Hi everyone,
>
> Just would like to request a security feature to help secure peoples github
> accounts more by supporting 2 factor authentication like the yubikey more
> information can be found from this link www.yubico.com/develop/ and goog
On Mon, Feb 18, 2013 at 1:39 PM, wrote:
> James Nylen writes:
>> - add "fancylib" as a subtree of "myprog"
>> - commit to "myprog" repo: "fancylib: don't crash as much"
>> - split these commits back out to "fancylib"
On Tue, Feb 5, 2013 at 6:44 AM, wrote:
> Junio C Hamano writes:
>
>>> Remove --annotate. This obviates the need for an --unannotate
>>> command. We really want a more generalized commit message rewrite
>>> mechanism.
>>
>> That may be a good goal as the end result, but wouldn't it be a bit
>>
On Tue, Jan 1, 2013 at 5:31 PM, wrote:
> Junio C Hamano writes:
>
>> "David A. Greene" writes:
>>
>>> From: James Nylen
>>>
>>> Teach git-subtree about --unannotate. This option strips a prefix
>>> from a commit message when doi
On Mon, Dec 31, 2012 at 8:15 PM, wrote:
> James Nylen writes:
>
>> Rather than adding a marker to each commit when splitting out the
>> commits back to the subproject, --unannotate removes the specified
>> string (or bash glob pattern) from the beginning of the fir
On Thu, Nov 1, 2012 at 2:12 PM, Thomas Adam wrote:
> Hi,
>
> On 1 November 2012 16:07, Ramkumar Ramachandra wrote:
>>
>> Hi,
>>
>> Some of my colleagues are lazy to fire up an editor and write proper
>> commit messages- they often write one-liners using `git commit -m`.
>> However, that line turn
On Fri, Oct 26, 2012 at 9:58 AM, David Michael Barr wrote:
> From a quick survey, it appears there are no more than 55 patches
> squashed into the submitted patch.
> As I have an interest in git-subtree for maintaining the out-of-tree
> version of vcs-svn/ and a desire to improve my rebase-fu, I a
On Tue, Oct 9, 2012 at 4:26 PM, James Nylen wrote:
> This new option does the reverse of --annotate, which is more useful
> when contributing back to a library which is also included in the
> repository for a larger project, and perhaps in other situations as
> well.
>
> Ra
On 10/11/2012 1:38 PM, Jim Vahl wrote:
For the sake of argument, I'll assume that a committing a change implies
that the file has passed the testing process. So my questions are:
You should not assume this. You / your developers should commit far
more frequently than you test and release vers
arge
project and the library project.
Signed-off-by: James Nylen
---
Let me know if gmail has munged this patch. You can also get at it
like this:
$ git remote add nylen git://github.com/nylen/git.git
$ git fetch nylen
$ git show nylen/subtree-unannotate
---
contrib/subtree/git-subtree.sh | 11
11 matches
Mail list logo