Johannes Schindelin wrote:
> On Mon, 21 Jan 2019, Eric Wong wrote:
> >http://hjrcffqmbrq6wope.onion/git/
> >
> > Tested with Netsurf and dillo.
>
> Nice.
>
> Do you also plan on taking care of the regular thread view? I still find
> it *very* hard to navigate it, and I have to admit tha
Hi,
Junio C Hamano wrote:
> Thomas Gummerer writes:
>> Jonathan Nieder wrote:
>>> Is this analogous to "git add --ignore-removal"? If so, can we just
>>> call it --ignore-removal?
>>
>> Yes, it seems like they are very similar.
>
> Hmm, I am not sure if the word "removal" makes sense in the con
Upgrade the packing_data lock to a recursive mutex to make it suitable
for current read_lock usages. Additionally remove the superfluous
#ifndef NO_PTHREADS guard around mutex initialization in
prepare_packing_data as the mutex functions themselves are already
protected.
Signed-off-by: Patrick Hog
ac77d0c37 ("pack-objects: shrink size field in struct object_entry",
2018-04-14) added an extra usage of read_lock/read_unlock in the newly
introduced oe_get_size_slow for thread safety in parallel calls to
try_delta(). Unfortunately oe_get_size_slow is also used in serial
code, some of which is ca
On Tue, Jan 22, 2019 at 06:07:14PM -0400, Joey Hess wrote:
> joey@darkstar:~/tmp/t> ls -l big-file
> -rw-r--r-- 1 joey joey 11811160064 Jan 22 17:48 big-file
> joey@darkstar:~/tmp/t> git status
> fatal: Out of memory, realloc failed
>
> This file is checked into git, but using a smudge/clean filte
On Wed, Jan 23, 2019 at 12:57:05AM -0500, Jeff King wrote:
> This uses designated initializers, which is a C99-ism, but one we've
> used previously and feel confident in. But...
>
> > +void clear_repository_format(struct repository_format *format)
> > +{
> > + string_list_clear(&format->unknown_
> From: Derrick Stolee
>
> The commit-graph file format v2 changes the v1 data only in the
> header information. Add tests that check the 'verify' subcommand
> catches corruption in the v2 header.
Ah, I should have read this patch before I wrote [1]. I think the commit
message of that patch shou
> +Version 2:
> +
> + 1-byte number (C) of "chunks"
> +
> + 1-byte reachability index version number:
> + Currently, the only valid number is 1.
> +
> + 1-byte (reserved for later use)
> + Current clients expect this value to be zero, and will not
> + try to read the commit-graph
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> This commit adds an azure-pipelines.yml file which is Azure DevOps'
> equivalent to Travis CI's .travis.yml.
>
> To make things a bit easier to understand, we refrain from using the
> `matrix` feature here because (wh
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> Let's not decide in the generic ci/ script how many jobs to run in
> parallel; it is easy enough to hand that information down via the
> `MAKEFLAGS`.
>
> Signed-off-by: Johannes Schindelin
> ---
> ci/run-build-and-t
"Johannes Schindelin via GitGitGadget"
writes:
> diff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh
> index fe65144152..bcdcc71592 100755
> --- a/ci/install-dependencies.sh
> +++ b/ci/install-dependencies.sh
> @@ -37,7 +37,8 @@ osx-clang|osx-gcc)
> brew update --quiet
>
"Johannes Schindelin via GitGitGadget"
writes:
> This patch series took wy more time than I had originally
> anticipated, but I think that in particular the advanced display of the test
> results and the reduction of the overall run time was worth it. Please let
> me know what you think a
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> As Unix shell scripting comes at a hefty price on Windows, we have to
> see where we can save some time to run the test suite.
>
> Let's skip the chain linting and the bin-wrappers/ redirection on
> Windows; this seem
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> We really need to be able to find the test helpers... Really. This
> change was forgotten when we moved the test helpers into t/helper/
>
> Signed-off-by: Johannes Schindelin
> ---
> t/test-lib.sh | 2 +-
> 1 file c
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> The name is hard-coded to reflect that we use Travis CI for continuous
> testing.
>
> In the next commits, we will extend this to be able use Azure DevOps,
> too.
>
> So let's adjust the name to make it more generic.
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> In the next commit, we want to teach Git's test suite to optionally
> output test results in JUnit-style .xml files. These files contain
> information about the time spent. So we need a way to measure time.
>
> While
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> The Windows job currently takes a whopping ~1h20m to complete. Which is
> *far* longer than the next-longest job takes (linux-gcc, ~35m). As such,
> it makes sense to start the Windows job first, to minimize the overa
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> This patch introduces a conditional arm that defines some environment
> variables and a function that displays the URL given the job id (to
> identify previous runs for known-good trees).
>
> For example, we do not ha
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> When building a PR, TRAVIS_BRANCH refers to the *target branch*.
> Therefore, if a PR targets `master`, and `master` happened to be tagged,
> we skipped the build by mistake.
>
> Fix this by using TRAVIS_PULL_REQUEST_
On Wed, Jan 23, 2019 at 10:57 AM Junio C Hamano wrote:
>
> Missing sign-off?
>
My mistake, forgot -s on format-patch. Will remember to add it next go-around.
> > +static int ref_to_worktree_map_cmpfnc(const void *unused_lookupdata, const
> > void *existing_hashmap_entry_to_test,
> > +
"Johannes Schindelin via GitGitGadget"
writes:
> From: Johannes Schindelin
>
> The Windows job currently takes a whopping ~1h20m to complete. Which is
> *far* longer than the next-longest job takes (linux-gcc, ~35m). As such,
> it makes sense to start the Windows job first, to minimize the overa
> The multi-pack-index provides a fast way to find an object among a large
> list of pack-files. It stores a single pack-reference for each object id, so
> duplicate objects are ignored. Among a list of pack-files storing the same
> object, the most-recently modified one is used.
>
> Create new su
> diff --git a/Documentation/git-multi-pack-index.txt
> b/Documentation/git-multi-pack-index.txt
> index 6186c4c936..cc63531cc0 100644
> --- a/Documentation/git-multi-pack-index.txt
> +++ b/Documentation/git-multi-pack-index.txt
> @@ -36,6 +36,17 @@ expire::
> have no objects referenced by t
> From: Derrick Stolee
>
> To repack using a multi-pack-index, first sort all pack-files by
> their modified time. Second, walk those pack-files from oldest
> to newest, adding the packs to a list if they are smaller than the
> given pack-size. Finally, collect the objects from the multi-pack-
>
> From: Derrick Stolee
>
> The 'git multi-pack-index expire' command looks at the existing
> mult-pack-index, counts the number of objects referenced in each
> pack-file, deletes the pack-fils with no referenced objects, and
> rewrites the multi-pack-index to no longer reference those packs.
Tha
From: Derrick Stolee
The commit-graph file format v2 changes the v1 data only in the
header information. Add tests that check the 'verify' subcommand
catches corruption in the v2 header.
Signed-off-by: Derrick Stolee
---
t/t5318-commit-graph.sh | 31 +++
1 file chan
From: Derrick Stolee
In anticipation of a new commit-graph file format version, create
a flag for the write_commit_graph() and write_commit_graph_reachable()
methods to take a version number.
When there is no specified version, the implementation selects a
default value. Currently, the only vali
From: Derrick Stolee
The commit-graph file format had some shortcomings which we now
correct:
1. The hash algorithm was determined by a single byte, instead
of the 4-byte format identifier.
2. There was no way to update the reachability index we used.
We currently only support gen
From: Derrick Stolee
The write_commit_graph() and write_commit_graph_reachable() methods
currently take two boolean parameters: 'append' and 'report_progress'.
We will soon expand the possible options to send to these methods, so
instead of complicating the parameter list, first simplify it.
Col
From: Derrick Stolee
Allo the commit-graph builtin to specify the file format version
using the '--version=' option. Specify the version exactly in
the verification tests as using a different version would change
the offsets used in those tests.
Signed-off-by: Derrick Stolee
---
Documentation/
From: Derrick Stolee
The write_commit_graph() method uses die() to report failure and
exit when confronted with an unexpected condition. This use of
die() in a library function is incorrect and is now replaced by
error() statements and an int return type.
Now that we use 'goto cleanup' to jump t
The commit-graph file format has some shortcomings that were discussed
on-list:
1. It doesn't use the 4-byte format ID from the_hash_algo.
2. There is no way to change the reachability index from generation numbers
to corrected commit date [1].
3. The unused byte in the
Ben Peart writes:
> From: Ben Peart
>
> Minor update to comment from V2. Also wrapped commit messages to be <80
> chars wide.
Perfect. Thanks.
Jean-Noël AVILA writes:
> These styling fixes were raised by warning of po4a when processing
> the files. Otherwise, there's no hurry in pushing them.
Yeah, but as we postpone it, all the topics in flight that wants to
touch documentation may get blocked (or cause this large patch to be
redone
Thomas Gummerer writes:
>> I had no idea what --overlay would mean and am still not clear on it.
>> Is this analogous to "git add --ignore-removal"? If so, can we just
>> call it --ignore-removal?
>
> Yes, it seems like they are very similar.
Hmm, I am not sure if the word "removal" makes sense
Following Stolee's wishes [1], I'll stick to the technical aspects here.
Patches 1-4 look correct technically to me, so let me start here.
[1] https://public-inbox.org/git/3aa0a7ea-6c30-2c61-0815-2b9ab8304...@gmail.com/
> +struct pack_info {
> + uint32_t orig_pack_int_id;
> + char *pack_n
As transform_todo_file() is only needed inside of rebase--interactive.c,
it is moved there from sequencer.c.
Signed-off-by: Alban Gruin
---
Unchanged since v4.
builtin/rebase--interactive.c | 26 +-
sequencer.c | 23 ---
sequencer.h
This refactors skip_unnecessary_picks() to work on a todo_list. As this
function is only called by complete_action() (and thus is not used by
rebase -p), the file-handling logic is completely dropped here.
Instead of truncating the todo list’s buffer, the items are moved to
the beginning of the l
edit_todo_list() is changed to work on a todo_list, and to handle the
initial edition of the todo list (ie. making a backup of the todo
list).
It does not check for dropped commits yet, as todo_list_check() does not
take the commits that have already been processed by the rebase (ie. the
todo list
This makes sequencer_make_script() write its script to a strbuf (ie. the
buffer of a todo_list) instead of a FILE. This reduce the amount of
read/write made by rebase interactive.
Signed-off-by: Alban Gruin
---
Unchanged since v4.
builtin/rebase--interactive.c | 13 ++-
sequencer.c
At the center of the "interactive" part of the interactive rebase lies
the todo list. When the user starts an interactive rebase, a todo list
is generated, presented to the user (who then edits it using a text
editor), read back, and then is checked and processed before the actual
rebase takes pla
The 'arg' field of todo_item used to store the address of the first byte
of the parameter of a command in a todo list. It was associated with
the length of the parameter (the 'arg_len' field).
This replaces the 'arg' field by 'arg_offset'. This new field does not
store the address of the paramet
This changes complete_action() to use edit_todo_list(), now that it can
handle the initial edit of the todo list.
Signed-off-by: Alban Gruin
---
Unchanged since v4.
sequencer.c | 21 +++--
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/sequencer.c b/sequencer.c
i
This refactors check_todo_list() to work on a todo_list to avoid
redundant reads and writes to the disk. The function is renamed
todo_list_check(). The parsing of the two todo lists is left to the
caller.
As rebase -p still need to check the todo list from the disk, a new
function is introduced,
complete_action() used functions that read the todo-list file, made some
changes to it, and wrote it back to the disk.
The previous commits were dedicated to separate the part that deals with
the file from the actual logic of these functions. Now that this is
done, we can call directly the "logic
This makes the structures todo_list and todo_item, and the functions
todo_list_release() and parse_insn_buffer(), accessible outside of
sequencer.c.
Signed-off-by: Alban Gruin
---
Unchanged since v4.
sequencer.c | 69 ++---
sequencer.h | 50 ++
Just like complete_action(), edit_todo_list() used a
function (transform_todo_file()) that read the todo list from the disk
and wrote it back, resulting in useless disk accesses.
This changes edit_todo_list() to call directly todo_list_write_to_file()
instead.
Signed-off-by: Alban Gruin
---
Squa
This moves the writing of the comment "Rebase $shortrevisions onto
$shortonto ($command_count commands)" from todo_list_write_to_file() to
append_todo_help().
shortrevisions, shortonto, and command_count are passed as parameters to
append_todo_help().
During the initial edit of the todo list, sho
This clears the number of items of a todo_list before parsing it to
allow to parse the same list multiple times without issues. As its
items are not dynamically allocated, or don’t need to allocate memory,
no additionnal memory management is required here.
Furthermore, if a line is invalid, the t
This refactors rearrange_squash() to work on a todo_list to avoid
redundant reads and writes. The function is renamed
todo_list_rearrange_squash().
The old version created a new buffer, which was directly written to the
disk. This new version creates a new item list by just copying items
from th
This refactors sequencer_add_exec_commands() to work on a todo_list to
avoid redundant reads and writes to the disk.
Instead of inserting the `exec' commands between the other commands and
re-parsing the buffer at the end, they are appended to the buffer once,
and a new list of items is created.
This refactors transform_todos() to work on a todo_list. The function
is renamed todo_list_transform().
As rebase -p still need to check the todo list from the disk, a new
function is introduced, transform_todo_file(). It is still used by
complete_action() and edit_todo_list() for now, but they
This introduces a new function to recreate the text of a todo list from
its commands and write it to a file. This will be useful as the next
few commits will change the use of the buffer in struct todo_list so it
will no longer be a mirror of the file on disk.
This functionality already exists in
"Jeff Hostetler via GitGitGadget" writes:
> +These high-level events are written to one or more Trace2 Targets
> +in a target-specific format. Each Trace2 Target defines a different
> +purpose-specific view onto the event data stream. In this mannor,
"In this manner"
> +a single set of Trace2
Thomas Gummerer wrote:
> On 01/22, Jonathan Nieder wrote:
>> I had no idea what --overlay would mean and am still not clear on it.
>> Is this analogous to "git add --ignore-removal"? If so, can we just
>> call it --ignore-removal?
>
> Yes, it seems like they are very similar. I'm happy to rename
On Wednesday, 23 January 2019 20:36:46 CET Junio C Hamano wrote:
> I somehow misread the title as "tiny asciidoc style (fixes)". This
> is a huge clean-up. Thanks for working on it.
>
These styling fixes were raised by warning of po4a when processing
the files. Otherwise, there's no hurry in
On 01/22, Jonathan Nieder wrote:
> Hi,
>
> Thomas Gummerer wrote:
>
> > Currently 'git checkout' is defined as an overlay operation, which
> > means that if in 'git checkout -- []' we have an
> > entry in the index that matches , but that doesn't exist in
> > , that entry will not be removed fro
From: Ben Peart
Commit fa655d8411 (checkout: optimize "git checkout -b ",
2018-08-16) introduced an unintentional change in behavior for 'checkout -b'
after doing 'clone --no-checkout'. Add a test to demonstrate the changed
behavior to be used in a later patch to verify the fix.
Signed-off-by:
From: Ben Peart
Minor update to comment from V2. Also wrapped commit messages to be <80
chars wide.
Base Ref: master
Web-Diff: https://github.com/benpeart/git/commit/fef76edbdc
Checkout: git fetch https://github.com/benpeart/git initial-checkout-v3 && git
checkout fef76edbdc
### Interdiff (v
From: Ben Peart
When doing a 'checkout -b' do a full checkout including updating the working
tree when doing the initial checkout. As the new test involves an filesystem
access, do it later in the sequence to give chance to other cheaper tests to
leave early. This fixes the regression in behavior
Junio C Hamano writes:
> Jean-Noël Avila writes:
>
>> This mainly refers to enforcing indentation on additional lines of
>> items of lists.
>>
>> Signed-off-by: Jean-Noël Avila
>> ---
>
> I somehow misread the title as "tiny asciidoc style (fixes)". This
> is a huge clean-up. Thanks for worki
Jean-Noël Avila writes:
> This mainly refers to enforcing indentation on additional lines of
> items of lists.
>
> Signed-off-by: Jean-Noël Avila
> ---
I somehow misread the title as "tiny asciidoc style (fixes)". This
is a huge clean-up. Thanks for working on it.
> diff --git a/Documentatio
Barret Rhoden writes:
>> So... I dunno.
>
> I guess if you swap the lines as well as change them,...
> ... Then it won't have the semantic knowledge that "one" == "1". If a user
> is ignoring a commit, we don't have an oracle that knows exactly what
> that commit did to determine what commit the
A user over there at the git-users ML is having troubles with the
wording of the `git check-ignore` manual page which, in their opinion,
fails to clearly communicate the twist about tracked files being not
eligible for ignored/non-ignored checks:
- Forwarded message from cl.robitai...@gmail.co
Ben Peart writes:
>> This is curious. The location the new special case is added is
>> different, and the way the new special case is detected is also
>> different, between v1 and v2. Are both of them significant? IOW,
>> if we moved the check down but kept using is_cache_unborn(), would
>> it
Jonathan Nieder writes:
> I'm nervous about the config with no associated warning or plan for
> phasing it out.
This was discussed long ago (in my panda-brain timescale) but my
recollection is to keep "checkout" default to the traditional
"overlay what was read from the tree on top of the curren
nbelakov...@gmail.com writes:
> From: Nickolai Belakovski
>
> Add an atom providing the path of the linked worktree where this ref is
> checked out, if it is checked out in any linked worktrees, and empty
> string otherwise.
> ---
Missing sign-off?
> +static int ref_to_worktree_map_cmpfnc(const
On Mon, Jan 21, 2019 at 02:50:07PM -0500, Ben Peart wrote:
> From: Ben Peart
>
> Commit fa655d8411 (checkout: optimize "git checkout -b ",
> 2018-08-16)
> introduced an unintentional change in behavior for 'checkout -b' after doing
> 'clone --no-checkout'. Add a test to demonstrate the changed
Torsten Bögershausen writes:
>> I'd still prefer to see a more terse[1] (and not capitalized) message
>> to be consistent with existing error messages and to keep the reported
>> errors more compact overall to make them easier to digest[2,3]:
>>
>> err 'sed option not portable (use only -n, -
Derrick Stolee writes:
> On 1/19/2019 3:21 PM, Ævar Arnfjörð Bjarmason wrote:
>> Improvements since v6:
>>
>> * Integrate my "commit-graph write: use pack order when finding
>> commits" patch, and per Junio's suggestion put it at the start so
>> it's easier to split the two apart.
>>
>>
Patrick Hogg writes:
> On Tue, Jan 22, 2019 at 5:43 PM Junio C Hamano wrote:
>>
>> Patrick Hogg writes:
>>
>> > As I mentioned in the prior thread I think that it will be simpler
>> > to simply use the existing lock in packing_data instead of moving
>> > read_mutex. I can go back to simply movi
The optional 'Extra Edge List' chunk of the commit graph file stores
parent information for commits with more than two parents. Since the
chunk is optional, write_commit_graph() looks through all commits to
find those with more than two parents, and then writes the commit
graph file header accordi
On January 23, 2019 11:00, Christopher Hagler wrote:
> Send the email to this address
> majord...@vger.kernel.org and it will work
> > On Jan 23, 2019, at 8:16 AM, Cody Kratzer
> > I've sent this same email 3 times. I don't think it works. I'm
> > researching this morning how to unsubscribe from t
Hi all,
On Wed, 23 Jan 2019, Johannes Schindelin via GitGitGadget wrote:
> * The Windows job was split into a job to build Git and 10 parallel
> jobs to run the test suite with the artifacts built by the first job.
> This reduces the overall run time from ~1h20 (which was the run time by
> th
Send the email to this address
majord...@vger.kernel.org and it will work
Sent from my iPhone
> On Jan 23, 2019, at 8:16 AM, Cody Kratzer wrote:
>
> I've sent this same email 3 times. I don't think it works. I'm
> researching this morning how to unsubscribe from this git group.
>
> CODY KRATZ
From: Johannes Schindelin
Symbolic links are still not quite as easy to use on Windows as on Linux
(for example, on versions older than Windows 10, only administrators can
create symlinks, and on Windows 10 you still need to be in developer
mode for regular users to have permission), but NTFS jun
For a long time already, we have tested Git's source code continuously via
Travis CI, see e.g. https://travis-ci.org/git/git/builds/421738884. It has
served us well, and more and more developers actually pay attention and
benefit from the testing this gives us.
It is also an invaluable tool for co
From: Johannes Schindelin
The name is hard-coded to reflect that we use Travis CI for continuous
testing.
In the next commits, we will extend this to be able use Azure DevOps,
too.
So let's adjust the name to make it more generic.
Signed-off-by: Johannes Schindelin
---
ci/install-dependencie
From: Johannes Schindelin
This patch introduces a conditional arm that defines some environment
variables and a function that displays the URL given the job id (to
identify previous runs for known-good trees).
For example, we do not have to install the git-lfs and gettext packages
on Azure Pipel
From: Johannes Schindelin
The Windows job currently takes a whopping ~1h20m to complete. Which is
*far* longer than the next-longest job takes (linux-gcc, ~35m). As such,
it makes sense to start the Windows job first, to minimize the overall
run time (which is now pretty safely the run time of th
From: Johannes Schindelin
We really need to be able to find the test helpers... Really. This
change was forgotten when we moved the test helpers into t/helper/
Signed-off-by: Johannes Schindelin
---
t/test-lib.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/test-lib.sh
From: Johannes Schindelin
Let's not decide in the generic ci/ script how many jobs to run in
parallel; it is easy enough to hand that information down via the
`MAKEFLAGS`.
Signed-off-by: Johannes Schindelin
---
ci/run-build-and-tests.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
From: Johannes Schindelin
When building a PR, TRAVIS_BRANCH refers to the *target branch*.
Therefore, if a PR targets `master`, and `master` happened to be tagged,
we skipped the build by mistake.
Fix this by using TRAVIS_PULL_REQUEST_BRANCH (i.e. the *source branch*)
when available, falling bac
From: Johannes Schindelin
Just like so many other OSS projects, we now also have a build badge.
Signed-off-by: Johannes Schindelin
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index f920a42fad..764c480c66 100644
--- a/README.md
+++ b/README.md
@@ -1
From: Johannes Schindelin
As Unix shell scripting comes at a hefty price on Windows, we have to
see where we can save some time to run the test suite.
Let's skip the chain linting and the bin-wrappers/ redirection on
Windows; this seems to shave of anywhere between 10-30% from the overall
runtim
From: Johannes Schindelin
It is a bit ridiculous to spin up a full-blown Perl instance (especially
on Windows, where that means spinning up a full POSIX emulation layer,
AKA the MSYS2 runtime) just to tell how large a given file is.
So let's just use the test-tool to do that job instead.
This c
From: Johannes Schindelin
The fact that Git's test suite is implemented in Unix shell script that
is as portable as we can muster, combined with the fact that Unix shell
scripting is foreign to Windows (and therefore has to be emulated),
results in pretty abysmal speed of the test suite on that p
From: Johannes Schindelin
When building Git with RUNTIME_PREFIX and starting a test helper from
t/helper/, it fails to detect the system prefix correctly.
This is the reason that the warning
RUNTIME_PREFIX requested, but prefix computation failed. [...]
to be printed.
In t0061, we did
From: Johannes Schindelin
This speeds up the tests by a bit on Windows, where running Unix shell
scripts (and spawning processes) is not exactly a cheap operation.
Signed-off-by: Johannes Schindelin
---
t/README | 9 +
t/test-lib.sh | 19 +--
2 files changed, 22 i
From: Johannes Schindelin
Every once in a while, the Azure Pipeline fails with some semi-random
error: timer thread did not terminate timely
This error message means that the thread that is used to emulate the
setitimer() function did not terminate within 1,000 milliseconds.
The most l
From: Johannes Schindelin
The JUnit XML format lends itself to be presented in a powerful UI,
where you can drill down to the information you are interested in very
quickly.
For test failures, this usually means that you want to see the detailed
trace of the failing tests.
With Travis CI, we pa
From: Johannes Schindelin
This commit adds an azure-pipelines.yml file which is Azure DevOps'
equivalent to Travis CI's .travis.yml.
To make things a bit easier to understand, we refrain from using the
`matrix` feature here because (while it is powerful) it can be a bit
confusing to users who ar
From: Johannes Schindelin
This will come in handy when publishing the results of Git's test suite
during an automated Azure DevOps run.
Note: we need to make extra sure that invalid UTF-8 encoding is turned
into valid UTF-8 (using the Replacement Character, \uFFFD) because
t9902's trace contains
From: Johannes Schindelin
Instead of a shallow fetch followed by a sparse checkout, we are
better off by using a separate, dedicated Pipeline that bundles
the SDK as a build artifact, and then consuming that build artifact
here.
In fact, since this artifact will be used a lot, we spent substanti
From: Johannes Schindelin
It seems that every once in a while in the Git for Windows SDK, there
are some transient file locking issues preventing the test clean up to
delete the trash directory. Let's be gentle and try again five seconds
later, and only error out if it still fails the second time
From: Johannes Schindelin
In the next commit, we want to teach Git's test suite to optionally
output test results in JUnit-style .xml files. These files contain
information about the time spent. So we need a way to measure time.
While we could use `date +%s` for that, this will give us only seco
From: Johannes Schindelin
The upcoming patches will allow building git.git via Azure Pipelines
(i.e. Azure DevOps' Continuous Integration), where variable names and
URLs look a bit different than in Travis CI.
Signed-off-by: Johannes Schindelin
---
ci/install-dependencies.sh | 3 ++-
ci/lib.s
Am 23.01.2019 um 15:16 schrieb Cody Kratzer:
> I've sent this same email 3 times. I don't think it works. I'm
> researching this morning how to unsubscribe from this git group.
Hi Cody,
https://git-scm.com/community says to subscribe you should send an email
with body content
subscribe git
to
unsubscribe git
I've sent this same email 3 times. I don't think it works. I'm
researching this morning how to unsubscribe from this git group.
CODY KRATZER WEB DEVELOPMENT MANAGER
866-344-3875 x145
c...@lightingnewyork.com
M - F 9 - 5:30
On Wed, Jan 23, 2019 at 5:51 AM Christopher Hagler
wrote:
>
> Unsubscrib
1 - 100 of 106 matches
Mail list logo
