bzr push should preserve group permissions of the target shared repository
Bug #771520 reported by
Daniel Cordeiro
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
This is a "wishlist" bug.
I'm trying to use a "shared repository" with other users on the same Linux group via sftp protocol. The shared repository have g+w permissions, but a new push creates a new branch without the proper group write permissions. It would be nice if the pushed branches could respect the group permissions from the "parent" shared repository (as it already does inside the branches).
I'm using
$ bzr --version
Bazaar (bzr) 2.3.1
Python interpreter: /usr/bin/python 2.7.1
Python standard library: /usr/lib/python2.7
Platform: Linux-2.
bzrlib: /usr/lib/
| summary: |
- bzr push shoud preserve group write permissions from its shared + bzr push should preserve group permissions of the target shared repository |
| Changed in bzr: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| tags: | added: check-for-breezy |
To post a comment you must log in.
