Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Development-branch #26

Closed
ineiti opened this issue Oct 7, 2015 · 1 comment
Closed

Development-branch #26

ineiti opened this issue Oct 7, 2015 · 1 comment

Comments

@ineiti
Copy link
Member

ineiti commented Oct 7, 2015

Is there any recommendation about keeping the feature-branches around once they are merged in the development-branch?
@bford
Copy link

bford commented Oct 7, 2015

I'd prefer to delete branches after they're merged. The important history is in the git revision history; no need for long-term branch clutter.

@ineiti ineiti closed this as completed Oct 8, 2015
ineiti pushed a commit that referenced this issue Mar 12, 2018
@darekzbik @ineiti
Data structure for permissions and specification of create user which…
edc6661 
… does not require private keys of administrator and user. Work related to #26 (#48)
jeffallen pushed a commit that referenced this issue Jun 6, 2018
@kc1212
Merge pull request #26 from dedis/exporting_fields
be4e175 
exporting fields so that Proof can be marshalled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bford @ineiti