Beloved,
I am writing this mail to you with heavy tears in my eyes and great
sorrow in my heart. As I informed you earlier, I am (Mrs.)Marianne
Jeanne,
suffering from long time Cancer. From all indications
my condition is really deteriorating and it's quite obvious
that I won't live more than
When checkout dwim is added in [1], it is restricted to only dwim when
certain conditions are met and fall back to default checkout behavior
otherwise. It turns out falling back could be confusing. One of the
conditions to turn
git checkout frotz
to
git checkout -b frotz origin/frotz
One of the problems with "git checkout" is that it does so many
different things and could confuse people specially when we fail to
handle ambiguation correctly.
One way to help with that is tell the user what sort of operation is
actually carried out. When switching branches, we always print
I need urgent partner for urgent business
On Fri, Nov 09 2018, Duy Nguyen wrote:
> On Fri, Nov 9, 2018 at 2:46 PM Ævar Arnfjörð Bjarmason
> wrote:
>> I'm planning to re-submit mine with some minor changes after the great
>> Documentation/config* move lands.
>>
>> As noted in
>>
On 10/11/2018 04:55, Duy Nguyen wrote:
> On Tue, Nov 6, 2018 at 3:07 PM Ramsay Jones
> wrote:
>> Also, this patch does not replace opterror() calls outside of
>> the 'parse-options.c' file with optname(). This tickles my
>> static-check.pl script, since optname() is an external function
>>
On Wed, Nov 07 2018, brian m. carlson wrote:
> On Mon, Nov 05, 2018 at 12:39:14PM +0100, Ævar Arnfjörð Bjarmason wrote:
>> On Sun, Nov 04 2018, brian m. carlson wrote:
>> > + {
>> > + "sha256",
>> > + /* "s256", big-endian */
>>
>> The existing entry/comment for sha1 is:
>>
On Sat, 10 Nov 2018 at 01:10, Stefan Beller wrote:
> I dialed back on the workflow, as we may want to explore it first
> before writing it down.
Makes sense.
FWIW, this iteration looks good to me.
Martin
Hi Alban,
On Fri, 9 Nov 2018, Alban Gruin wrote:
> p3400 makes a copy of the current repository to test git-rebase
> performance, and creates new branches in the copy with `git checkout
> -b'. If the original repository has branches with the same name as the
> script is trying to create, this
The script generate-cmdlist.sh needs input text files in UNIX line
ending to work correctly. It's been fine even with core.autocrlf set
because Documentation/git-*.txt is forced LF conversion.
But this leaves out gitk.txt and also Documentation/*config.txt that
recently becomes new input for this
Dear friend,
I am Abel Brent, a NATO soldier serving in Afghanistan. I and my
Comrades, we are seeking your assistance to help us
receive/invest our funds in your country in any lucrative
business. Please if this proposal is acceptable by you, kindly
respond back to me for more details.
On Sat, Nov 10, 2018 at 10:23:06PM -0800, Elijah Newren wrote:
> If --tag-of-filtered-object=rewrite is specified along with a set of
> paths to limit what is exported, then any tags pointing to old commits
> that do not contain any of those specified paths cause problems. Since
> the old tagged
On Sat, Nov 10, 2018 at 10:23:07PM -0800, Elijah Newren wrote:
> Logic to replace a filtered commit with an unfiltered ancestor is useful
> elsewhere; put it into a function we can call.
OK. I had to stare at it for a minute to make sure there was not an
edge case with looking at "p" versus
On Sat, Nov 10, 2018 at 10:23:09PM -0800, Elijah Newren wrote:
> If file paths are specified to fast-export and a ref points to a commit
> that does not touch any of the relevant paths, then that ref would
> sometimes fail to be exported. (This depends on whether any ancestors
> of the commit
On Sat, Nov 10, 2018 at 10:23:11PM -0800, Elijah Newren wrote:
> Knowing the original names (hashes) of commits, blobs, and tags can
> sometimes enable post-filtering that would otherwise be difficult or
> impossible. In particular, the desire to rewrite commit messages which
> refer to other
On Sat, Nov 10, 2018 at 10:36 PM Jeff King wrote:
>
> On Sat, Nov 10, 2018 at 10:23:04PM -0800, Elijah Newren wrote:
>
> > Signed-off-by: Elijah Newren
> > ---
> > Documentation/git-fast-export.txt | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git
On Sun, Nov 11, 2018 at 08:05:04AM +0100, tbo...@web.de wrote:
> From: Torsten Bögershausen
>
> When printing variables which contain a size, today "unsigned long"
> is used at many places.
> In order to be able to change the type from "unsigned long" into size_t
> some day in the future, we
On Sat, Nov 10, 2018 at 7:21 PM Fredi Fowler wrote:
> Is there any way to create pull request to git man (https://git-scm.com/docs)?
That website is maintained as a project separate from Git, so you can
report issues specific to the website, or create pull requests, at its
project page
On Sat, Nov 10, 2018 at 10:23:04PM -0800, Elijah Newren wrote:
> Signed-off-by: Elijah Newren
> ---
> Documentation/git-fast-export.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/git-fast-export.txt
> b/Documentation/git-fast-export.txt
> index
On Sat, Nov 10, 2018 at 10:23:05PM -0800, Elijah Newren wrote:
> ABORT and ERROR happen to have the same value, but come from differnt
> enums. Use the one from the correct enum.
Yikes. :)
This is a good argument for naming these SIGNED_TAG_ABORT, etc. But this
is obviously an improvement in
On Sat, Nov 10, 2018 at 10:23:03PM -0800, Elijah Newren wrote:
> Signed-off-by: Elijah Newren
> ---
> Documentation/git-fast-import.txt | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-fast-import.txt
> b/Documentation/git-fast-import.txt
>
On Sat, Nov 10, 2018 at 10:23:02PM -0800, Elijah Newren wrote:
> This is a series of ten patches representing two doc corrections, one
> pedantic fix, three real bug fixes, one micro code refactor, and three
> new features. Each of these ten changes is relatively small in size.
> These changes
On Sat, Nov 10, 2018 at 10:23:12PM -0800, Elijah Newren wrote:
> fast-export output is traditionally used as an input to a fast-import
> program, but it is also useful to help gather statistics about the
> history of a repository (particularly when --no-data is also passed).
> For example, two of
On Sat, Nov 10, 2018 at 10:44 PM Jeff King wrote:
>
> On Sat, Nov 10, 2018 at 10:23:06PM -0800, Elijah Newren wrote:
>
> > If --tag-of-filtered-object=rewrite is specified along with a set of
> > paths to limit what is exported, then any tags pointing to old commits
> > that do not contain any of
Is there any way to create pull request to git man (https://git-scm.com/docs)?
I found there some inconsistencies. For example, almost in all pages
are using [no-], but at https://git-scm.com/docs/git-merge each
command (with [no-] or without) write separately.
There are some same
If file paths are specified to fast-export and a ref points to a commit
that does not touch any of the relevant paths, then that ref would
sometimes fail to be exported. (This depends on whether any ancestors
of the commit which do touch the relevant paths would be exported with
that same ref
git filter-branch has a nifty feature allowing you to rewrite, e.g. just
the last 8 commits of a linear history
git filter-branch $OPTIONS HEAD~8..HEAD
If you try the same with git fast-export, you instead get a history of
only 8 commits, with HEAD~7 being rewritten into a root commit. There
ABORT and ERROR happen to have the same value, but come from differnt
enums. Use the one from the correct enum.
Signed-off-by: Elijah Newren
---
builtin/fast-export.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/fast-export.c b/builtin/fast-export.c
index
Signed-off-by: Elijah Newren
---
Documentation/git-fast-export.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-fast-export.txt
b/Documentation/git-fast-export.txt
index ce954be532..677510b7f7 100644
--- a/Documentation/git-fast-export.txt
+++
Logic to replace a filtered commit with an unfiltered ancestor is useful
elsewhere; put it into a function we can call.
Signed-off-by: Elijah Newren
---
builtin/fast-export.c | 37 ++---
1 file changed, 22 insertions(+), 15 deletions(-)
diff --git
Knowing the original names (hashes) of commits, blobs, and tags can
sometimes enable post-filtering that would otherwise be difficult or
impossible. In particular, the desire to rewrite commit messages which
refer to other prior commits (on top of whatever other filtering is
being done) is very
Signed-off-by: Elijah Newren
---
Documentation/git-fast-import.txt | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-fast-import.txt
b/Documentation/git-fast-import.txt
index e81117d27f..7ab97745a6 100644
--- a/Documentation/git-fast-import.txt
+++
This is a series of ten patches representing two doc corrections, one
pedantic fix, three real bug fixes, one micro code refactor, and three
new features. Each of these ten changes is relatively small in size.
These changes predominantly affect fast-export, but there's a couple
small changes for
If file paths are specified to fast-export and multiple refs point to a
commit that does not touch any of the relevant file paths, then
fast-export can hit problems. fast-export has a list of additional refs
that it needs to explicitly set after exporting all blobs and commits,
and when it tries
fast-export output is traditionally used as an input to a fast-import
program, but it is also useful to help gather statistics about the
history of a repository (particularly when --no-data is also passed).
For example, two of the types of information we may want to collect
could include:
1)
If --tag-of-filtered-object=rewrite is specified along with a set of
paths to limit what is exported, then any tags pointing to old commits
that do not contain any of those specified paths cause problems. Since
the old tagged commit is not exported, fast-export attempts to rewrite
such tags to an
On Sat, Nov 10, 2018 at 10:23:08PM -0800, Elijah Newren wrote:
> If file paths are specified to fast-export and multiple refs point to a
> commit that does not touch any of the relevant file paths, then
> fast-export can hit problems. fast-export has a list of additional refs
> that it needs to
From: Torsten Bögershausen
When printing variables which contain a size, today "unsigned long"
is used at many places.
In order to be able to change the type from "unsigned long" into size_t
some day in the future, we need to have a way to print 64 bit variables
on a system that has "unsigned
On Sat, Nov 10, 2018 at 10:23:10PM -0800, Elijah Newren wrote:
> git filter-branch has a nifty feature allowing you to rewrite, e.g. just
> the last 8 commits of a linear history
> git filter-branch $OPTIONS HEAD~8..HEAD
>
> If you try the same with git fast-export, you instead get a history
39 matches
Mail list logo
