On Sun, Jul 12, 2015 at 12:21:33AM +0200, X H wrote:
How are the permission handled, is it git that is asking to create a file
read only or rw on the remote or is it the environment with umask ans so on
that decides it, or Windows when the drive is mounted with noacl?
Generally, git follows
On Sun, Jul 12, 2015 at 3:15 PM, Duy Nguyen pclo...@gmail.com wrote:
On Thu, Jul 9, 2015 at 5:58 PM, Karthik Nayak karthik@gmail.com wrote:
-static int show_reference(const char *refname, const struct object_id *oid,
- int flag, void *cb_data)
-{
...
-
- if
Hello All,
As part of GSoC I'm working on the Unification of 'for-each-ref', 'tag -l'
and 'branch -l'. Sorry for the lack of update since Jun 14, was a
little busy with an exam I had. Now thats over, I will be working more
on the project.
Current Progress:
1. Building ref-filter.{c,h} from
On Sun, Jul 12, 2015 at 04:54:02PM +0700, Duy Nguyen wrote:
On Sun, Jul 12, 2015 at 10:27 AM, Eric Sunshine sunsh...@sunshineco.com
wrot In this case, it's easy enough to side-step the issue since there's no
need to call ref_exists() if the new branch was created successfully
(since we
On Sun, Jul 12, 2015 at 7:17 AM, Duy Nguyen pclo...@gmail.com wrote:
I guess if you can have multiple arguments after ':' in an atom, then
you have wiggle room for future. But it looks like you only accept one
argument after ':'.. (I only checked the version on 'pu'). Having an
alignment atom
OSCON is coming up soon (the week of the 20th) in Portland, and I want
to let people know that there's going to be a small Git table in the
exhibit hall, connected to the GitHub booth. I'll be manning the table
both days (Wednesday and Thursday the 22nd and 23rd), telling people
about how great
On Sun, Jul 12, 2015 at 9:01 PM, Jeff King p...@peff.net wrote:
OSCON is coming up soon (the week of the 20th) in Portland, and I want
to let people know that there's going to be a small Git table in the
exhibit hall, connected to the GitHub booth. I'll be manning the table
both days
On Thu, Jul 9, 2015 at 5:58 PM, Karthik Nayak karthik@gmail.com wrote:
-static int show_reference(const char *refname, const struct object_id *oid,
- int flag, void *cb_data)
-{
...
-
- if (match_pattern(filter-name_patterns, refname)) {
-
On Sun, Jul 12, 2015 at 2:39 PM, Duy Nguyen pclo...@gmail.com wrote:
On Thu, Jun 25, 2015 at 6:43 PM, Karthik Nayak karthik@gmail.com wrote:
Add support to sort by version using the v:refname and
version:refname option. This is achieved by using the
'version_cmp()' function as the
From: Ilya Bobyr ilya.bo...@gmail.com
It is not very likely that any of the *=?! Characters would be useful
in the argument short or long names. On the other hand, there are
already argument hints that contain the = sign. It used to be
impossible to include any of the *=?! signs in the
(resend, +everybody)
On Sun, Jul 12, 2015 at 10:27 AM, Eric Sunshine sunsh...@sunshineco.com wrote:
So, if I understand your concern correctly, then you are worried that,
following the git-branch invocation, ref_exists() could return the
wrong answer with a pluggable ref-backend since it might
On Fri, Jul 10, 2015 at 10:14 PM, Junio C Hamano gits...@pobox.com wrote:
Christian Couder christian.cou...@gmail.com writes:
On Thu, Jul 9, 2015 at 12:27 PM, Karthik Nayak karthik@gmail.com wrote:
Mentored-by: Christian Couder christian.cou...@gmail.com
Mentored-by: Matthieu Moy
On Sun, Jul 12, 2015 at 8:47 AM, Duy Nguyen pclo...@gmail.com wrote:
Another thing, the atom value is also used for sorting. When used for
sorting, I think these padding spaces should not be generated or it
may confuse the sort algorithm. Left alignment may be ok, right or
center alignment (in
On Thu, Jun 25, 2015 at 6:43 PM, Karthik Nayak karthik@gmail.com wrote:
Add support to sort by version using the v:refname and
version:refname option. This is achieved by using the
'version_cmp()' function as the comparing function for qsort.
If these v:refname and version:refname are from
Hi,
(Sorry for the late reply. Caught a nasty stomach bug that kept me in
bed for a while )
On Thu, Jul 9, 2015 at 2:00 PM, Junio C Hamano gits...@pobox.com wrote:
What I pushed out tonight should have SQUASH??? (or fixup!) that
splits this into appropriate steps in your series. Please check.
Eric Sunshine sunsh...@sunshineco.com writes:
Did you want to drop the final patch[*1*] which retires
--ignore-other-worktrees in favor of --force before letting this
graduate to 'master'?
Yeah, thanks for catching it.
By the way, v1 of the follow-on series which replaces git checkout
with
René Scharfe l@web.de writes:
Check if a matched token is followed by a delimiter before advancing the
pointer arg. This avoids accepting composite words like allnew or
defaultcontext.
Signed-off-by: Rene Scharfe l@web.de
---
diff.c | 7 ++-
1 file changed, 6 insertions(+),
From: ilya.bo...@gmail.com Sent: Sunday, July 12, 2015 10:39 AM
From: Ilya Bobyr ilya.bo...@gmail.com
It is not very likely that any of the *=?! Characters would be
useful
in the argument short or long names. On the other hand, there are
already argument hints that contain the = sign. It
Simon A. Eugster simon...@gmail.com writes:
+... As the keeper of
+the canonical history, you need to view the history from the remote
+as `ours` (i.e. our shared canonical history), while what you did
+on your side branch as `theirs` (i.e. one contributor's work on top
+of it).
-b
ilya.bo...@gmail.com writes:
From: Ilya Bobyr ilya.bo...@gmail.com
It is not very likely that any of the *=?! Characters would be useful
in the argument short or long names. On the other hand, there are
already argument hints that contain the = sign. It used to be
impossible to include
Paul Tan pyoka...@gmail.com writes:
However, I am reluctant to blindly replace assert(!state-field)
with free(state-field). Are there cases where we _must_ call a
function that sets these fields at most once?
I wouldn't say we are blindly replacing them.
I said I was, not you and me. If
21 matches
Mail list logo
