What's in git.git (Aug 2008, #01; Tue, 05)

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

What's in git.git (Aug 2008, #01; Tue, 05)

Junio C Hamano
Thanks to many people, we have accumulated quite a few fixes that are
appropriate for 1.6.0 stabilization effort but at the same time apply
equally well to 1.5.6 series.  We might want to do 1.5.6.5 to flush them
while we are at it.

I am planning to tag 1.6.0-rc2 tomorrow evening.  I noticed that both gitk
and git-gui have fixes and many updated translations that I intend to
pull before tagging -rc2.

* The 'maint' branch has these fixes since the last announcement.

Anders Melchiorsen (1):
  Documentation: fix diff.external example

Brandon Casey (1):
  t/t4202-log.sh: add newline at end of file

Ciaran McCreesh (1):
  Make git-add -i accept ranges like 7-

Jeff King (1):
  init: handle empty "template" parameter

Jim Meyering (1):
  git-cvsimport.perl: Print "UNKNOWN LINE..." on stderr, not stdout.

Johannes Schindelin (1):
  sort_in_topological_order(): avoid setting a commit flag

Jonathan Nieder (1):
  git-diff(1): "--c" -> "--cc" typo fix

Junio C Hamano (6):
  make sure parsed wildcard refspec ends with slash
  Documentation: clarify diff --cc
  Update my e-mail address
  Start 1.5.6.5 RelNotes to describe accumulated fixes
  builtin-name-rev.c: split deeply nested part from the main function
  RelNotes 1.5.6.5 updates

Linus Torvalds (1):
  diff.renamelimit is a basic diff configuration

Mike Ralphson (1):
  Documentation: typos / spelling fixes in older RelNotes

Pierre Habouzit (1):
  git-submodule: move ill placed shift.

Pieter de Bie (1):
  git-name-rev: allow --name-only in combination with --stdin

René Scharfe (1):
  git-name-rev: don't use printf without format

Stephan Beyer (1):
  builtin-revert.c: typofix

Steve Haslam (1):
  Propagate -u/--upload-pack option of "git clone" to transport.


* The 'master' branch has these since the last announcement
  in addition to the above.

Abhijit Menon-Sen (4):
  Git.pm: localise $? in command_close_bidi_pipe()
  Fix hash slice syntax error
  Fix typo in perl/Git.pm
  Fix typos in INSTALL

Anders Melchiorsen (2):
  Flush output in start_async
  Add output flushing before fork()

Avery Pennarun (2):
  Teach "git diff -p" Pascal/Delphi funcname pattern
  git-svn: Abort with an error if 'fetch' parameter is invalid.

Brandon Casey (1):
  Teach fsck and prune that tmp_obj_ file names may not be 14 bytes long

David D. Kilzer (1):
  Fix race condition in t9119-git-svn-info.sh

Dmitry Potapov (1):
  correct access right for git-svn-dcommit test

Eric Wong (2):
  git-svn: properly set path for "info" command
  t9119: conditionally re-enable test depending on svn(1) version

Giuseppe Bilotta (2):
  diff: add ruby funcname pattern
  diff: chapter and part in funcname for tex

Johannes Schindelin (2):
  clone: Add an option to set up a mirror
  clone --bare: Add ".git" suffix to the directory name to clone into

Jon Jensen (1):
  Fix reference to Everyday Git, which is an HTML document and not a man
    page.

Lee Marlow (11):
  bash completion: remove unused function _git_diff_tree
  bash completion: Add more long options for 'git log'
  bash completion: Add completion for 'git grep'
  bash completion: Add completion for 'git clone'
  bash completion: Add completion for 'git clean'
  bash completion: Add completion for 'git init'
  bash completion: Add completion for 'git revert'
  bash completion: More completions for 'git stash'
  bash completion: Add completion for 'git archive'
  bash completion: Add completion for 'git ls-files'
  bash completion: Add completion for 'git mv'

Mike Ralphson (1):
  Documentation: typos / spelling fixes

Steffen Prohaska (1):
  Modify mingw_main() workaround to avoid link errors

Steven Grimm (1):
  Optimize sha1_object_info for loose objects, not concurrent repacks

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|

Query: GIT bare repro

Pandita, Vikram
Hi GIT users

I want to use GIT for my team for distributed development.
The team members are working at different sites.

Would appreciate help on following:

1) Could you point me to some document/example for doing so? This should be very common scenario I assume.

2) I understand that every developer will need a BARE public repro and a personal repro.
        - How does one push new branches to a bare public repro?

        - do Public and personal repro need to be on the same machine?

        - Can one "PROTECT" specific branches in public repro like master?
           One may not want the MASTER of public repro to be overwritten?

Regards,
Vikram

N�����r��y���b�X��ǧv�^�)޺{.n�+����ا���ܨ}���Ơz�&j:+v�������zZ+��+zf���h���~����i���z��w���?����&�)ߢf�
Reply | Threaded
Open this post in threaded view
|

Re: Query: GIT bare repro

Christian MICHON
On Wed, Aug 6, 2008 at 9:46 AM, Pandita, Vikram <[hidden email]> wrote:
> Hi GIT users
>
> I want to use GIT for my team for distributed development.
> The team members are working at different sites.
>
> Would appreciate help on following:
>
> 1) Could you point me to some document/example for doing so? This should be very common scenario I assume.

Please read http://book.git-scm.com/3_distributed_workflows.html

--
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Reply | Threaded
Open this post in threaded view
|

RE: Query: GIT bare repro

Pandita, Vikram
> From: Christian MICHON [mailto:[hidden email]]
> Sent: Wednesday, August 06, 2008 1:59 PM
>
> On Wed, Aug 6, 2008 at 9:46 AM, Pandita, Vikram <[hidden email]> wrote:
> > Hi GIT users
> >
> > I want to use GIT for my team for distributed development.
> > The team members are working at different sites.
> >
> > Would appreciate help on following:
> >
> > 1) Could you point me to some document/example for doing so? This should be very common scenario I
> assume.
>
> Please read http://book.git-scm.com/3_distributed_workflows.html

Thanks Christian
Sure this will help.

>
> --
> Christian
> --
> http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [hidden email]
More majordomo info at  http://vger.kernel.org/majordomo-info.html