[OpenAFS] Bug Submission to OpenAFS
Jeffrey Altman
jaltman@secure-endpoints.com
Mon, 3 Oct 2011 18:39:36 +0200
--Apple-Mail-1-50362260
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
Nathan:
Please send bugs via email to openafs-bugs@openafs.org. The receipt of the e=
mail will generate the ticket in the tracking system.
Please submit as much data as you can without giving away private informatio=
n. Do not attach large files. Instead put them somewhere in AFS or elsewhe=
re that is publicly accessible and includevthe location in the report.
Thank you.
Jeffrey Altman
Sent from my iPad
On Oct 3, 2011, at 5:30 PM, Nathaniel Hatley <nathaniel.hatley@gmail.com> wr=
ote:
> Good Morning,
>=20
> I have been working with Jeffrey Altman on various bugs that we've uncover=
ed on the OpenAFS Redirector with our new environment here at UNC Charlotte.=
Given Jeffrey's recent submission of the redirector to the public tree, I w=
ill need to start filing bugs with the OpenAFS bug tracking system. I have n=
ot participated in OpenAFS' systems before, and would like to know the corre=
ct methods of performing various actions.
>=20
> For example: I currently know of a bug that I've experienced that I see a=
n open ticket for in the bug tracker. I do not have an account on the track=
er, so I cannot post stating that I have also experienced this issue. Would=
this be the correct behaviour? Or should I just submit an additional bug t=
o openafs-bugs and reference the previous bug number?
> =20
> Additionally, to what level of detail should I attempt to give when I subm=
it bugs? Typically if it is relevant, I will create procmon logs of the iss=
ue and have them accessible via http. I also attempt to thoroughly describe=
the environment with which I reproduced the issue.
> =20
> =20
> Thank you,
> Nathan Hatley
--Apple-Mail-1-50362260
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><body bgcolor=3D"#FFFFFF"><div>Nathan:</div><div><br></div><div>Please=
send bugs via email to <a href=3D"mailto:openafs-bugs@openafs.org">openafs-=
bugs@openafs.org</a>. The receipt of the email will generate the ticke=
t in the tracking system.</div><div><br></div><div>Please submit as much dat=
a as you can without giving away private information. Do not attach la=
rge files. Instead put them somewhere in AFS or elsewhere that is publ=
icly accessible and includevthe location in the report.</div><div><br></div>=
<div>Thank you.</div><div><br></div><div>Jeffrey Altman<br><br>Sent from my i=
Pad</div><div><br>On Oct 3, 2011, at 5:30 PM, Nathaniel Hatley <<a href=3D=
"mailto:nathaniel.hatley@gmail.com">nathaniel.hatley@gmail.com</a>> wrote=
:<br><br></div><div></div><blockquote type=3D"cite"><div><p>Good Morning,</p=
><p>I have been working with Jeffrey Altman on various bugs that we've uncov=
ered on the OpenAFS Redirector with our new environment here at UNC Charlott=
e. Given Jeffrey's recent submission of the redirector to the public t=
ree, I will need to start filing bugs with the OpenAFS bug tracking system.&=
nbsp; I have not participated in OpenAFS' systems before, and would like to k=
now the correct methods of performing various actions.</p>
<div>For example: I currently know of a bug that I've experienced that=
I see an open ticket for in the bug tracker. I do not have an account=
on the tracker, so I cannot post stating that I have also experienced this i=
ssue. Would this be the correct behaviour? Or should I just subm=
it an additional bug to openafs-bugs and reference the previous bug number?<=
/div>
<div> </div><div>Additionally, to what level of detail should I attempt=
to give when I submit bugs? Typically if it is relevant, I will creat=
e procmon logs of the issue and have them accessible via http. I also a=
ttempt to thoroughly describe the environment with which I reproduced the is=
sue.</div>
<div> </div><div> </div><div>Thank you,</div><div>Nathan Hatley</d=
iv>
</div></blockquote></body></html>=
--Apple-Mail-1-50362260--